Disabling, using an explicit indication,  hybrid automatic repeat request (harq) acknowledgments for  packets for which  acknowledgements are supported at a network or higher layer

ABSTRACT

A first communications device including a transmitter identifies a packet flow for which end to end packet retransmission is supported. The first wireless communications device transmits an explicit indication in a downlink message to a second wireless communications device, to skip Hybrid Automatic Repeat Request (HARQ) feedback for data, corresponding to the first packet flow, said data being directed to the second wireless communications device. In some embodiments, said explicit indication to skip Hybrid Automatic Repeat Request (HARQ) feedback for data is a predetermined value in a predetermined field of a downlink control information (DCI) scheduling message. In some embodiments, the predetermined field is a PDSCH-to-HARQ feedback timing indicator field. HARQ suppression is applied for the first packet flow at a radio link layer and/or MAC layer, e.g., by the second communications device in response to the predetermined value indicating HARQ suppression being recovered from the predetermined field.

RELATED APPLICATIONS

The present application claims the benefit of U.S. Provisional PatentApplication Ser. No. 62/713,519 filed Aug. 1, 2018 in its entirety.

FIELD

The present application relates to communications methods and apparatus,and more particularly, to methods and apparatus for disabling radio linkcontrol (RLC) and/or Hybrid Automatic Repeat Request (HARQ) for flowssupporting an end to end acknowledgment, e.g., TCP packet flows.

BACKGROUND

Various types of packet flows support end to end retransmission ofpackets. TCP/IP streams normally support end to end retransmission ofpackets with an end device in a communications session that fails toreceive a complete packet signaling the other end of the communicationssession of the packet transmission failure.

While packet retransmission can be triggered at a high level bycommunication from one end device to another end device, ACK/NACKmechanisms may be, and often are, supported at various layers for one ormore individual communications links which may form a part of an end toend communications path.

ACK/NACK mechanisms systems with retransmission for data that is notsuccessfully received is particularly common for wireless links. Suchmechanisms which are often applied at a relatively low communicationslayer, e.g., physical layer or mac layer, can be useful particularly forpacket streams that do not support end to end retransmission of lost ormissing packets. Such ACK/NACK and retransmission mechanisms applied foran individual link can also add to the reliability of communicationspacket flows that support end to end retransmission of packets in theevent of a communications failure.

While retry and re-transmission over links might seem to be desirablefrom a reliability perspective, they can introduce delays in thatre-transmissions over individual links can take time as a device waitsto process an ACK/NACK for a link before potentially transmittingadditional data. Furthermore, the ACK/NACK signaling and potentialretransmission itself has the potential to introduce delays, it alsorequires the use of communications resources to perform the ACK/NACKsignaling as well as processing resources to handle such signaling andpotentially support retransmission on an individual link. While delaysmay not be an issue for some packet flows, in the case of packet flowswhere a low latency is desired, implementing retry mechanisms onindividual links can introduce delays, consume bandwidth, and/or consumeprocessing resources which might be used for other activities, e.g., tosupport communication of other data.

From the above discussion it should be appreciated that the use ofACK/NACK and retry mechanisms on individual links can be desirable insome cases, for some packet flows it would be desirable if the use ofACK/NACK signaling and/or retransmission over individual links of apacket path, e.g., including multiple links, could be avoided orlimited, e.g., to avoid possible delays and/or minimize processingrequirements as compared to embodiments where full ACK/NACKfunctionality and retransmission is supported on the individual linksthat make up an end to end a packet transmission path.

In view of the above discussion it should be appreciated that there is aneed to address multiple technical problems relating to the use ofACK/NACK and/or retransmission on individual links of a packet path. Thetechnical problems include but are not limited to: i) identifying packetstreams for which disabling or avoiding the use of ACK/NACK and/orretransmission functionality would be beneficial; ii) controlling one ormore devices to disable or avoid applying ACK/NACK and/or retransmissionfunctionality to data corresponding one or more packet streams; and iii)limiting the processing or operations which are required to be performedin response to an ACK/NACK corresponding to a link when retransmissionwith regard to the link is not to be supported.

From the above it should be appreciated that method and/or apparatuswhich can be used to address one, more or all of the above discussedproblems and/or otherwise facilitate communication of packet streams indevices which have the ability to support ACK/NACK signaling would bedesirable.

SUMMARY

In various embodiments a first communications device including atransmitter, such as a base station or UE, identifies a packet flow forwhich end to end packet retransmission is supported. The packet flow maybe one of a plurality of such flows with RLC acknowledgement suppressiontechniques and/or HARQ suppression techniques being applied to one, moreor all such flows. For example HARQ suppression is applied selectivelyin some embodiments to links corresponding to packet flows with lowlatency requirements while HARQ suppression is not applied to otherflows with end to end packet retransmission which have lower latencyrequirements.

In some embodiments the packet flow to which HARQ suppression is appliedis a TCP/IP packet flow for which end to end packet retransmission issupported. To avoid delays that may be associated with attempting toretransmit data due to a transmission failure of some data over theradio link between the base station and access point HARQ retransmissionof data, e.g., portions of packets may be, and sometimes, are disabledin the first communications device. As part of the HARQ suppressionprocess, one or more portions of the HARQ process maybe avoided orsuppressed. For example in some cases ACK/NACK signaling is disabled andthe processing of such signals is avoided. In other embodiments ACK/NACKsignaling may still occur with the device receiving the ACK/NACKdisregarding the signals and/or intentionally refraining fromretransmitting data in response to such signals and/or proceeding withtransmitting additional data over the link without waiting for an ACKwith respect to data that was previously transmitted on the link.

In at least some cases where HARQ suppression is applied to a packetflow, the packet retransmission method supported by the end devices inthe packet flow is relied upon to assure overall end to endcommunications reliability without depending on the HARQ capabilitiesthat could have been used on individual links, e.g., such as a radiolink between a base station or UE, which form part of a communicationspath between the two end devices.

In various embodiments HARQ suppression is applied to a communicationslink between two communications devices with the communications linkbeing one of a plurality of links on a packet path that connects one ofthe first and second devices with a third communications device. Invarious embodiments one of the first and second devices is a UE (UserEquipment device) and the other one of the first and second devices is abase station. The third communications device may be, for example,another UE.

Thus, in some embodiments the first communications device which is usedto implement one or more methods is a base station, such as a gNodeB(gNB). The base station may be, and sometimes is, an intermediate nodeon the communications path between a third device, e.g., another UE, andthe second device. In such a case the third device is an end device,e.g., the source of a TCP/IP packet flow and the second device isanother end communications device for the TCP/IP packet flow with thesecond device being the destination device to which the first packetflow is directed. In such an embodiment HARQ retransmission may be, andsometimes is, disabled on the downlink with respect to the TCP/IP packetflow which supports end to end retransmission.

While HARQ retransmission and related signaling maybe and sometimes isdisabled for all TCP/IP packet flows which support end to end packetretransmission, in some embodiments the HARQ retransmission is onlyfully or partially disabled for packet flows subject to low latencyrequirements, e.g., TCP/IP packet flows with latency requirements belowa predetermined threshold level used to identify packet flows for whichHARQ retransmission should be fully or partially suppressed.

While in some embodiments, e.g., HARQ downlink suppression embodiments,the first communications device is a base station, in other embodiments,e.g., HARQ uplink suppression embodiments, the first communicationsdevice is a UE or other end communications device.

Thus in some embodiments, e.g., uplink HARQ suppression embodiments, thefirst communications device is a UE or other end node and the secondcommunications device is a base station. In at least some suchembodiments the third communications device is, e.g., another UE, whichis the other end node to which packets originating at the firstcommunications device are directed. In such an embodiment HARQretransmission may be, and sometimes, is disabled or at HARQ signalingor processing is at least partially suppressed on the uplink withrespect to a packet flow that supports end to end retransmission oflost, missing or corrupted packets.

While at least some packet flows for which an end to end retransmissionprocess is supported may, and often will, have HARQ retransmissiondisabled or suppressed on a portion of the overall communications pathbetween the end devices in accordance with the invention, other packetflows such as UDP packet flows for which end to end retransmission isnot supported will be communicated without disabling HARQ over one ormore links, e.g., radio links, on the path between the source of thepacket flow and the destination of the packet flow.

In accordance with some features of the invention, in some but notnecessarily all embodiments the transmission and use of ACKs/NACKs forthe portion of the communications path, e.g., an individual radio link,between first communications device and the second communications deviceis intentionally disabled for traffic flows for which end to end packetretransmission is supported, e.g., at least some TCP/IP packet flows. Inthis way failure to communicate data corresponding to a portion of apacket between the first communications device, e.g., base station, andthe second communications device, e.g., UE, will not triggerretransmission, by the first communications device, of the data whichwas not successfully communicated over the individual link over which aHARQ retry mechanism was disabled and thus not enabled. While avoidingautomatic retransmissions over the individual link between the first andsecond communications devices, which would normally be triggered bydetection of a NACK indicating failure to communicate data over thelink, has the advantage of reducing latency by eliminating the layer ofHARQ processing and retransmission. Thus with respect to flows for whichHARQ signaling or processing is partially or fully suppressed, e.g.,disabled, overall throughput may be enhanced by avoiding delays suchACK/NACK signaling and potential data retransmission might introduce tothe packet flow. In such cases the implemented end to end packetretransmission mechanism still provides a good degree of reliability toinsure that a packet will be successfully communicated while avoidingthe need for ACK/NACK signaling and processing with regard to anindividual portion, e.g., individual radio link between a base stationand UE, of the overall communications path between the source and enddestination device corresponding to a packet flow being communicated.

In various embodiments a first communications device including atransmitter, such as a base station or UE, identifies a packet flow forwhich end to end packet retransmission is supported. HARQ suppression isapplied at a radio link layer and/or MAC layer. One or more HARQsuppression techniques, including disabling ACK/NACK signaling for apacket flow going over a radio link and/or limiting processing by, forexample, disregarding NACKs, send with regard to data communication overthe radio link, are described. HARQ suppression is applied selectivelyin some embodiments to links corresponding to packet flows with lowlatency requirements while HARQ suppression is not applied to otherflows which have more flexibility with regard to latency, e.g., whichcan allow for more latency than the low latency flows. The methods canbe applied to links of a packet flow between two end devices where thelinks to which HARQ suppression are applied can be uplink and/ordownlinks forming a portion of the end to end communications path. Aspart of the HARQ suppression process, one or more portions of the HARQprocess may be disabled, avoided, or fully or partially suppressed.ACK/NACK signaling can be disabled and/or ignored depending on theembodiment.

An exemplary communications method, in accordance with some embodiments,comprises: identifying, at a first wireless communications device (e.g.,a base station such as a gNB or eNB) including a transmitter, a firsttraffic flow; and transmitting, from the first wireless communicationsdevice, an explicit indication in a downlink message to a secondwireless communications device (e.g., a UE) to skip Hybrid AutomaticRepeat Request (HARQ) feedback for data, corresponding to the firsttraffic flow, said data being directed to the second wirelesscommunications device. In some such embodiments, said explicitindication to skip Hybrid Automatic Repeat Request (HARQ) feedback fordata is a predetermined value in a predetermined field of a downlinkcontrol information (DCI) scheduling message. An exemplarycommunications system, in accordance with some embodiments, comprises: afirst wireless communications device comprising: a transmitter; and aprocessor configured to: identify, at the first wireless communicationsdevice (e.g., a base station such as a gNB or eNB) including thetransmitter, a first traffic flow; and operate said transmitter totransmit, from the first wireless communications device, an explicitindication in a downlink message to a second wireless communicationsdevice (e.g., a UE) to skip Hybrid Automatic Repeat Request (HARQ)feedback for data, corresponding to the first traffic flow, said databeing directed to the second wireless communications device.

A first communications device including a transmitter, e.g. a basestation, identifies a packet flow for which end to end packetretransmission is supported. The first wireless communications devicetransmits an explicit indication in a downlink message to a secondwireless communications device, e.g., a UE, to skip Hybrid AutomaticRepeat Request (HARQ) feedback for data, corresponding to the firstpacket flow, said data being directed to the second wirelesscommunications device. In some embodiments, said explicit indication toskip Hybrid Automatic Repeat Request (HARQ) feedback for data is apredetermined value in a predetermined field of a downlink controlinformation (DCI) scheduling message. In some embodiments, thepredetermined field is a PDSCH-to-HARQ feedback timing indicator field.HARQ suppression is applied for the first packet flow at a radio linklayer and/or MAC layer, e.g., by the second communications device inresponse to the predetermined value indicating HARQ suppression beingrecovered from the predetermined field.

While the transmitting device may assign the data corresponding to apacket flow with an end to end retransmission mechanism, e.g., a TCP/IPpacket flow, the receiving device may not support the no ACK/NAKtransmission process. In such a case the receiving device, particularlyin the case where in existing HARQ process ID was repurposed for the newHARQ process which does not require transmission of ACKs/NACKs may notrealize that it is not required to transmit an ACK/NACK in response to adata transmission and may transmit ACK/NACK. If such unnecessarytransmission for a particular traffic flow occurs, the transmittingdevice will receive the transmitted ACK/NACK. However, ACKs/NACKsreceived for flows for which HARQ retransmission is not supported willbe disregarded by the HARQ process corresponding to the flow for whichACK/NACK are not required and retransmission is not supported, e.g., isdisabled. In such cases since the received ACK/NACK corresponds to aHARQ processes which does not involve retransmission, whether or not aNACK is received, in at least some embodiments receipt of a NACKcorresponding to such a flow will not result in a retransmission by thebase station of the data which was not successfully received.

In the case of a TCP/IP packet flow for which HARQ over the link betweenthe base station and end communications device has been disabled,failure of the end device to receive a complete packet may and normallywill result in the second communications device signaling to the otherend communications device that a packet was not received and the othercommunications device, e.g., the third communications device which maybe another UE will retransmit the lost packet.

While a base station may assign packet flows with end to endretransmission capability to a HARQ process which does not requiretransmission of ACKs/NACKs and normally will not involve processing ofACKs/NACKs, one or more packet flows which do not support an end to endtransmission are communicated using a HARQ process which supports use ofACK/NACK between the first communications device, e.g., base station,and second communications device, e.g., UE. Thus HARQ processes whichsupport ACK/NACKs are used where the data being communicated is notsufficiently protected by one or more other retransmission methods,e.g., end to end packet retransmission methods.

While various features discussed in the summary are used in someembodiments it should be appreciated that not all features are requiredor necessary for all embodiments and the mention of features in thesummary should in no way be interpreted as implying that the feature isnecessary or critical for all embodiments.

Numerous additional features and embodiments are discussed in thedetailed description which follows.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates an exemplary 3-way handshake between an initiator anda listener used with the TCP protocol.

FIG. 2 is a drawing including HARQ processes.

FIG. 3 illustrates the approach of marking TCP segments carrying ACKsusing a “Marking” flag, which is set to a 1, when the TCP segmentcontains and ACK and is set to a 0 when the TCP segment does not carryan ACK.

FIG. 4 is a drawing of an exemplary communications system in accordancewith various exemplary embodiments.

FIG. 5 is a drawing including four exemplary acknowledgment modeprotocol data units, each including a ‘No RLC ACK required (NRAR)’ 1 bitfield, in accordance with an exemplary embodiment.

FIG. 6 is a drawing of an exemplary user equipment (UE) device inaccordance with an exemplary embodiment.

FIG. 7 is a drawing of an exemplary base station, e.g., a gNB or eNB, inaccordance with an exemplary embodiment.

FIG. 8 is a drawing of an exemplary server, e.g., an Application server(AS) in accordance with an exemplary embodiment.

FIG. 9 is a flowchart of an exemplary method of operating acommunications system, e.g., a communications system including a basestation, e.g., a gNB or eNB, and a user equipment (UE) device, todisable Hybrid Automatic Repeat Request (HARQ) and/or Radio Link Control(RLC) ACKs for an identified traffic flow, e.g., a identified TCPtraffic flow supporting ACK which satisfies an additional servicecriteria, e.g., Quality Control Indicator (QCI)/5QI indicatingultra-reliable low latency communication (URLLC) in downlink inaccordance with an exemplary embodiment.

FIG. 10 is a flowchart of an exemplary method of operating acommunications system, e.g., a communications system including a basestation, e.g., a gNB or eNB, and a user equipment (UE) device, todisable Hybrid Automatic Repeat Request (HARQ) and/or Radio Link Control(RLC) ACKs for an identified traffic flow, e.g., a identified TCPtraffic flow supporting ACK which satisfies an additional servicecriteria, e.g., Quality Control Indicator (QCI)/5QI indicatingultra-reliable low latency communication (URLLC) in uplink in accordancewith an exemplary embodiment.

FIG. 11 is a flowchart of an exemplary method of operating a UE devicein a communications system, e.g., a new radio (NR) or LTE communicationssystem supporting selective disabling of HARQ ACK/NACK, e.g., foridentified TCP downlink traffic flows, satisfying predeterminedcriteria, in accordance with an exemplary embodiment.

FIG. 12 is a flowchart of an exemplary method of operating acommunications system in accordance with an exemplary embodiment, saidmethod including disabling Hybrid Automatic Repeat Request (HARQ) inselected traffic flows.

FIG. 13 is a drawing of an exemplary assembly of components which may beincluded in a wireless communications device, e.g., a base station suchas the exemplary base station of FIG. 7, and implement steps of anexemplary method, e.g., steps of the method of the flowchart of FIG. 12.

FIG. 14 is a drawing of an exemplary assembly of components which may beincluded in a wireless communications device, e.g., a UE such as the UEof FIG. 6, and implement steps of an exemplary method, e.g., steps ofthe method of the flowchart of FIG. 12.

FIG. 15 is a flowchart of an exemplary method of operating a firstcommunications device including a transmitter in accordance with variousexemplary embodiments, said method including disabling Hybrid AutomaticRepeat Request (HARQ) in selected traffic flows.

FIG. 16 is a drawing of an exemplary assembly of components which may beincluded in a wireless communications device, e.g., a base station suchas the exemplary base station of FIG. 7, and implement steps of anexemplary method, e.g., steps of the method of the flowchart of FIG. 15.

FIG. 17 is a drawing of an exemplary assembly of components which may beincluded in a wireless communications device, e.g., a UE such as the UEof FIG. 6, and implement steps of an exemplary method, e.g., steps ofthe method of the flowchart of FIG. 15.

FIG. 18 is a flowchart of an exemplary communications method, e.g., acommunications method supporting disabling of HARQ for some trafficflows, in accordance with an exemplary embodiment.

FIG. 19 is a drawing of an exemplary assembly of components which may beincluded in a wireless communications device, e.g., a base station suchas the exemplary base station of FIG. 7, and implement steps of anexemplary method, e.g., steps of the method of the flowchart of FIG. 18.

FIG. 20 is a drawing of an exemplary assembly of components which may beincluded in a wireless communications device, e.g., a UE such as the UEof FIG. 6, and implement steps of an exemplary method, e.g., steps ofthe method of the flowchart of FIG. 18.

FIG. 21 is a flowchart of an exemplary communications method inaccordance with an exemplary embodiment, said method including disablingHybrid Automatic Repeat Request (HARQ) in selected traffic flows.

FIG. 22 is a drawing of an exemplary assembly of components which may beincluded in a wireless communications device, e.g., a base station suchas the exemplary base station of FIG. 7, and implement steps of anexemplary method, e.g., steps of the method of the flowchart of FIG. 21.

FIG. 23 is a flowchart of an exemplary method of operating a firstwireless communications device including a transmitter in accordancewith an exemplary embodiment, e.g., an exemplary method of operating thefirst wireless communications device to signal suppression and suppressRLC ACK/NACK corresponding to selected acknowledged mode protocol dataunits (AM PDUs), in accordance with an exemplary embodiment.

FIG. 24 is a drawing of an exemplary assembly of components which may beincluded in a first wireless communications device, e.g., a base stationsuch as the exemplary base station of FIG. 7 or a UE such as theexemplary UE of FIG. 6, and implement steps of an exemplary method,e.g., steps of the method of the flowchart of FIG. 23.

FIG. 25 is a drawing illustrating exemplary wireless communicationsdevices in which one or more HARQ processes, e.g., K HARQ processes, maybe, and sometimes are, designated and used, e.g., temporarily designatedand used, as HARQ suppression processes, in which HARQ ACK/NACK issuppressed, in accordance with an exemplary embodiment.

FIG. 26 is a drawing illustrating an example of the first and secondcommunications devices of FIG. 25, in which 4 of the 16 HARQ processeshave been designated as HARQ suppression processes, and furtherillustrates assignment of a first type of packet flow to a designatedHARQ suppression process, and assignment of a second type of packet flowto a HARQ process which does not suppress feedback of ACK/NACK for data.

FIG. 27 is a drawing illustrating exemplary wireless communicationsdevices in which some HARQ processes are dedicated HARQ processes with acorresponding ID intended for a flow for which suppression of ACK/NACKis required or desired and ACK/NACK feedback in response to data is notcommunicated or used, while other HARQ processes are normal HARQprocesses in which ACK/NACK feedback in response to data is supported,in accordance with an exemplary embodiment.

FIG. 28 is a drawing illustrating an example of the first and secondcommunications devices of FIG. 27, in which 4 of the 20 HARQ processesare dedicated HARQ suppression processes, and further illustratingassignment of a first type of packet flow to a dedicated HARQsuppression process, and assignment of a second type of packet flow to aHARQ process which does not suppress feedback of ACK/NACK for data.

FIG. 29 is a drawing illustrating exemplary wireless communicationsdevices in which some HARQ processes are dedicated HARQ processes with acorresponding HARQS process ID intended for a flow for which suppressionof ACK/NACK is required or desired and ACK/NACK feedback in response todata is not communicated or used, while other HARQ processes are normalHARQ processes with a corresponding HARQ process ID in which ACK/NACKfeedback in response to data is supported, said HARQS process ID andsaid HARQ process ID, being communicated in different variables and/ordifferent fields, in accordance with an exemplary embodiment.

FIG. 30 is a drawing illustrating an example of the first and secondcommunications devices of FIG. 29, in which 4 of the 20 HARQ processesare dedicated HARQ suppression processes, and further illustratingassignment of a first type of packet flow to a dedicated HARQsuppression process, and assignment of a second type of packet flow to aHARQ process which does not suppress feedback of ACK/NACK for data.

FIG. 31 is a drawing illustrating exemplary wireless communicationsdevices, exemplary signaling and exemplary steps of an exemplary methodin which RLC ACK/NACK is conditionally suppressed based on the value ofa No RLC Acknowledgment Required (NRAR) indicator bit included anAcknowledged Mode Data (AMD) PDU in accordance with an exemplaryembodiment.

DETAILED DESCRIPTION

Various aspects and/or features of Transmission Control Protocol (TCP)will now be described. TCP is a connection-oriented protocol whichrequires the well-known 3-way handshake. Drawing 100 of FIG. 1illustrates an exemplary 3-way handshake between an initiator device 102and a listener device 104. In step 106 initiator device 102 is operatedto initiate a connection with listener device 104. In step 108, listenerdevice 104 is operated to listen. In step 110, device 102 generates andsends Synchronization (SYN) message 112, which is successfully receivedby device 104 in step 114. In response to the successfully received SYNmessage 112, in step 116, the Transmission Control Block (TCB) isinitialized to SYN-RECEIVED state. In step 118, device 104 generates andsends Synchronization-Acknowledgement (SYN-ACK) message 120 to device102. In step 122, device 102 successfully receives SYN-ACK message 120.In step 124, device 122 returns a success code. In step 126, device 102generates and sends ACK message 128 to device 104. In step 130 device104 successfully receives ACK message 128. In response to thesuccessfully received ACK message 128, in step 132, TCB transitions tothe established state. In steps 134 and 136, the devices (104, 102) areoperated to exchange data packets 138 with each other.

In IPv4, the TCP ACK size is approximately 52 bytes, which includes 20bytes for the IP header+32 bytes for the TCP header. In IPv6, the TCPACK size is approximately 72 bytes, which includes 40 bytes for the IPheader+32 bytes for the TCP header.

A failure in any of the 3-steps, e.g., ACK not received, results inretransmission of the packet(s).

Internet Engineering Task Force Request for Comments (IETF RFC) 366provides a few ways of implementing Automatic Repeat Query (ARQ), TCPre-transmission mechanism at link layer: stop and wait ARQ, Go-Back NARQ, Selective Repeat ARQ, . . .

TCP Re-transmissions are governed by timer, which in turn are affectedby round trip time (RTT). RTT=(α)(old_RTT)+(1−α)(new_round_trip_sample).A longer RTT reduces throughput. Throughput<((C×MSS)/(RTT×sqrt(π)).

Various aspects of Long Term Evolution/New Radio Automatic RepeatRequest+Hybrid Automatic Repeat Request (LTE/NR ARQ+HARQ) will now bedescribed. 4G and 5G networks serve as a “transport” network to transmitvarious IP and non-IP packets. FIG. 2 is a drawing 200 including HARQprocesses.

Radio Link Control Acknowledged Mode (RLC (AM)) provides ARQ(re-transmission based on Selective Repeat (SR)) and re-ordering. Inaddition, Medium Access Control Layer-Physical Layer (MAC-PHY) provideHybrid-Automatic Repeat Request (HARQ). In LTE, Frequency DivisionDuplex (FDD): synchronous, there are 8 HARQ processes andre-transmission is allowed after 8 msec (4 msec for (n+4) response+4msec for grant-to-transmission delay). In LTE, Time Division Duplex(TDD): asynchronous given the asymmetrical uplink/downlink (UL/DL)split, 2 mechanisms were devised. The first mechanism includesAcknowledgement/Negative Acknowledgement (ACK/NACK) bundling, and alogical AND operation is used for each downlink codewordacknowledgments. The second mechanism includes AC/NACK multiplexing, andspatial layer ACK/NACKs are bundled. In NR asynchronous HARQ is used;there are 16 HARQ processes (default=8); and Downlink ControlInformation (DCI) format 1_0, and 1_1 includes a Physical DownlinkShared Channel-to-Hybrid Automatic Repeat Request (PDSCH-to-HARQ)feedback timing indicator which provides either which Physical UplinkControl Channel (PUCCH) slot (n+k) OR pre-defined slots {1-8} in whichto transmit ACK/NACK.

When TCP is sent over LTE/NR network, not withstanding packet-drops inCore Network, with Radio Access Network (RAN), the following threemechanisms get employed to govern transmissions: i) HARQ (at the PHY/MAClayers); ii) ARQ (at the RLC layer); and iii) TCP SYN_ACK/ACK (at the IPlayer).

For UE to server transmission, there may be, and sometimes are, lost TCPpackets. If the TCP packet loss occurs at the PHY/MAC layer, thisresults in only HARQ-based re-transmissions. If the TCP packet lossoccurs at the RLC layer, this results in HARQ+RLC (AM-mode) basedre-transmissions. And if the packet loss occurs at the IP layer, e.g.,somewhere in the network, this results in HARQ+RLC (AM mode)+TCP basedre-transmissions. The TCP packet loss and correspondingre-transmissions, cause delay in packet delivery. The delay in packetdelivery increase RTT, which decreases throughput, and the decreasedthroughput may, and sometimes does, cause congestion.

Drawing 300 of FIG. 3 illustrates the approach of marking TCP segmentscarrying ACKs using a “Marking” flag, which is set to a 1, when the TCPsegment contains and ACK and is set to a 0 when the TCP segment does notcarry an ACK.

In accordance with a feature of some embodiments, of the presentinvention, unnecessary packet TCP re-transmissions at the 3GPP transportnetwork level are not performed.

FIG. 4 is a drawing of an exemplary communications system 400 inaccordance with various exemplary embodiments. Exemplary communicationssystem 400 includes a plurality of user equipment (UE) devices (UE 1402, . . . , UE N 404), a plurality of base stations supporting a 5Gradio interface (gNB 1 406, . . . , gNB M 408), a 5G core (5GC) network410, and a plurality of application servers (AS 1 412, . . . , AS N414). Each of the UE devices, e.g., UE 1 402, supports communicationsusing: a Physical (PHY) layer, a Medium Access Control (MAC) layer, aRadio Link Control (RLC) layer, a Packet Data Convergence Protocol(PDPC) layer, a Radio Resource Control (RRC) layer, a Service DataAdaption Protocol (SDAP) layer, an Internet Protocol (IP) layer, and aTransmission Control Protocol (TCP) layer. The PHY layer is consideredLayer 1; the MAC, RLC, PDCP, and SDAP layers are considered Layer 2; andthe RRC layer is considered Layer 3.

Each of the base stations, e.g., gNB 1 406, supports communicationsusing: a PHY layer, a MAC layer, a RLC layer, a PDCP layer, a PDPClayer, a RRC layer, and a SDAP layer. Each of the application servers,e.g., AS 1 412, supports communications using: layer 1, layer 2, an IPlayer and a TCP layer.

Although FIG. 4 is used to describe the invention in the context of NewRadio (NR) terminology, the invention may, and sometimes is used in anLTE system which in not a NR system, e.g., a 4G LTE system using eNBsinstead of gNBs.

Exemplary novel features and/or aspects in accordance with someembodiments of the present invention Include one or more of: (i) methodsand/or apparatus directed to selectively disabling Radio Link ControlAcknowledgment Mode (RLC AM); ii) method and/or apparatus directed toselectively disabling Hybrid Automatic Repeat RequestAcknowledgment/Negative Acknowledgment (HARQ ACK/NACK); and iii) methodsand/or apparatus directed to selectively disabling both RLC AM and HARQACK/NACK.

Three alternative novel approaches to selectively disabling HybridAutomatic Repeat Request Acknowledgment/Negative Acknowledgment (HARQACK/NACK) will now be described. In a first approach, each of theuplink/downlink (UL/DL) operations are changed to disable HARQ automaticrepeat request (ARQ) in affected channels. In a second approach, onlyessential areas are changed to disable HARQ automatic request, and thebehavior is introduced on the receiver where even if HARQ-ACK was sent,the corresponding fields and associated logic is ignored. In a thirdapproach, since HARQ originates at the MAC layer, the HARQ processassignment behavior is fundamentally changed such that Transport Blocks(TBs) don't get slotted to a HARQ process.

High level steps involved in the propose solutions include: i) detectionat an eNBs/gNB for DL and at UE for UL that a given packet is a TCP ACKand any additional service criteria (e.g. Quality Control Indicator(QCI)/5QI indicates Utra-Reliable Low-Latency Communication (URLLC)packets); ii) upon such detection, dynamically disabling HARQ and/or RLCACKS for send of such packets prior to transmission for both UL and DLdirections; and iii) change in behavior at receiving end to account forthe above.

Examples of URLLC packets include, e.g., packets belonging to anaugmented reality or virtual reality stream, which are communicated overa high bandwidth low latency channel. Another type of exemplaryadditional service criteria includes, e.g. services for which thepenalty for not providing the ACK is low, e.g., GMAIL, web browsing, anews CNN website, YOUTUBE web browsing, etc.

In some embodiments, whether or not to selectively disable both radiolink control acknowledgment mode and HARQ ACK/NACK is to be governed bya new parameter in gNBs Operations Administration and Maintenance (OA&M)configuration.

An approach of disabling Acknowledgment (ACK) for Radio Link Control(RLC) Acknowledgment Mode (AM) by modifying Acknowledgment Mode Data(AMD) Protocol Data Unit (PDU) will now be described.

If a sender matches the selected Packet Data Convergence Protocol (PDCP)packet to Radio Link Control (RLC) Unacknowledged Mode (UM) mode, thenby default there won't be an RLC-level acknowledgment. So, in such ascenario no additional action needs to be taken.

If the sender matches the selected PDCP packet to RLC Acknowledged Mode(AM) mode, then in one category of solutions, a new toggle bit ‘No RLCACK required’, abbreviated as ‘NRAR’ is added to the different kinds ofRLC AMD PDU (c.f. 3GPP TS 38.322v15.2.0 section 6.2.2.4). The remainderbits of the newly added Octet are Reserved for future use.

‘NRAR’ is a 1-bit value. The default value for NRAR is 0, whichcommunicates RLC ACK expected. A value of 1 for NRAR communicates RLCACK not required.

For RLC AMD PDUs with ‘NRAR’ set to 1, the sending RLC entity shall notexpect ACK report from the receiving RLC entity in RLC STATUS PDU.

The receiving RLC entity shall not include S/N of AMD PDUs whengenerating RLC STATUS PDU (if requested).

FIG. 5 is a drawing 500 including four exemplary acknowledgment modeprotocol data units (502, 542, 562, 582), each including a ‘No RLC ACKrequired (NRAR)’ 1 bit field (509, 523, 571, 595), in accordance with anexemplary embodiment.

Exemplary AM PDU 502 includes a 12 bit sequence number (SN) and does notinclude a segment offset (SO). Column 503, which corresponds to AM PDU502, indicates that each row (504, 506, 508, 510, 512, . . . , 514)includes an octet of 8 bits. Octet 1 of row 504 includes a Data/Control(D/C) flag bit, a polling (P) bit, a 2 bit segment information field,and 4 bits for communicating part of the sequence number. Octet 2 of row506 includes 8 bits for communicating part of the sequence number. Octet3 of row 508 includes the 1 bit NRAR followed by 7 reserved bits. Theadditional rows (510, 512, . . . 514) convey data.

Exemplary AM PDU 542 includes a 12 bit sequence number and does includea segment offset. Column 543, which corresponds to AM PDU 542, indicatesthat each row (544, 546, 548, 550, 552, 554, 556, . . . , 558) includesan octet of 8 bits. Octet 1 of row 544 includes a Data/Control bit, apolling bit, a 2 bit segment information field, and 4 bits forcommunicating part of the sequence number. Octet 2 of row 546 includes 8bits for communicating part of the sequence number. Octet 3 of row 548includes 8 bit of the segment offset. Octet 4 of row 550 includes 8 bitof the segment offset. Octet 5 of row 552 includes the 1 bit NRARfollowed by 7 reserved bits. The additional rows (554, 556, . . . , 558)convey data.

Exemplary AM PDU 562 includes an 18 bit sequence number (SN) and doesnot include a segment offset (SO). Column 563, which corresponds to AMPDU 562, indicates that each row (564, 566, 568, 570, 572, . . . , 574)includes an octet of 8 bits. Octet 1 of row 564 includes a Data/Control(D/C) flag bit, a polling (P) bit, a 2 bit segment information field, 2reserved bits, and 2 bits for communicating part of the sequence number.Octet 2 of row 566 includes 8 bits for communicating part of thesequence number. Octet 3 of row 568 includes 8 bits for communicatingpart of the sequence number. Octet 4 of row 570 includes the 1 bit NRARfollowed by 7 reserved bits. The additional rows (572, 574, . . . , 576)convey data.

Exemplary AM PDU 582 includes an 18 bit sequence number and does includea segment offset. Column 583, which corresponds to AM PDU 582, indicatesthat each row (584, 586, 588, 590, 592, 594, 596, 598, . . . , 599)includes an octet of 8 bits. Octet 1 of row 584 includes a Data/Controlbit, a polling bit, a 2 bit segment information field, 2 reserved bits,and 2 bits for communicating part of the sequence number. Octet 2 of row566 includes 8 bits for communicating part of the sequence number. Octet3 of row 588 includes 8 bits for communicating part of the sequencenumber. Octet 4 of row 590 includes 8 bit of the segment offset. Octet 5of row 592 includes 8 bit of the segment offset. Octet 6 of row 594includes the 1 bit NRAR followed by 7 reserved bits. The additional rows(596, 598, . . . , 599) convey data.

An approach of disabling HARQ in all affected uplink and downlinkprocedures will now be described. In this category of solutions, the UEreceives an explicit indication to skip HARQ feedback for one or moreHARQ process IDs. In one aspect, for dynamic scheduling of DL, a newDownlink Control Information (DCI) field ‘HARQ Off Indicator’ is addedto the following DCI formats, which is applicable to both TDD and FDD.

DCI format 1_0 (38.212 7.3.1.2.1) for Cell-Radio Network TemporaryIdentifier (C-RNTI), Configured Scheduling Radio Network TemporaryIdentifier (CS-RNTI) (set when ‘Semi-Persistent Scheduling (SPS) HARQOff Indicator’ received in Resource Radio Control Information Element(RRC IE) ‘SPS-Config’).

DCI format 1_1 (38.212 7.3.1.2.1) for C-RNTI, CS-RNTI (set when ‘SPSHARQ Off Indicator’ received in RRC IE ‘SPS-Config’).

In various embodiments, the HARQ Off indictor is a 1 bit indicator,which is set when HARQ feedback is not required in response to theconcerned transmission. If the HARQ Off indicator is set, then the HARQprocess number field, and the Physical Downlink Shared CHannel(PDSCH)-to-HARQ_feedback timing indicator field are ignored.

The corresponding UE behavior is as follows. When the UE decodes DCIformat 1_0 or 1_1 with the HARQ Off indicator set, the UE shall notinclude HARQ-ACK in Uplink Control information (UCI) for Code BlockGroups/Transport Blocks (CBGs/TBs) scheduled in that DCI.

Radio Resource Control Information Elements ‘Semi-PersistentScheduling-Config’ (RRC IE ‘SPS-Config’) allows upper layers to informlower layers of when and what configuration is to be used when applyingSPS scheduling. In accordance with a feature of some embodiments, theHARQ disabling can be, and sometime is, performed semi-statically byadding an additional parameter, in accordance with a feature of thepresent invention, ‘SPS HARQ Off Indicator’ to the ‘SPS-Config’ RRC IE.

In the event of UL HARQ ACK/NACK reported by gNB/eNB, for e.g., inresponse to autonomous UL transmissions, the Autonomous Uplink-UplinkControl Information (AUL-UCI) that accompanies the Autonomous UplinkPhysical Uplink Shared Channel (AUL PUSCH) indicates the disabling of ULHARQ feedback via a new parameter called ‘AUL HARQ Off Indicator” whichserves the same purpose.

In a second category of solutions, a specific value indicated via ahigher layer parameter Slot-timing-value-K1 is used to indicate to theUE that HARQ feedback is not required whenever this value is received inDCI format 1_0 or 1_1 in the DCI field ‘PDSCH-to-HARQ_feedback timingindicator’. Thus no additional field needs to be introduced in the DCIformat itself.

Corresponding expected UE behavior, illustrated via change to TS 38.213clauses 9.1.2, 9.1.3.1 is as follows: If the UE receives DCI format 1_0or 1_1 scrambled with either C-RNTI or CS-RNTI withPDSCH-to-HARQ_feedback timing indicator set to [X], then the UE shallnot include HARQ-ACK in UCI for Code Block Groups/Transport Blocks(CBGs/TBs) scheduled in that Downlink Control Information (DCI).Alternatively, UE always reports and ACK.

Another solution, which will now be described, includes ignoringHARQ-ACK even when a HARQ-ACK is received in the affected UL+DLprocedures. In this category of solutions, no explicit changes are madeto the DL/UL scheduling and HARQ feedback procedures at Layer 1 (L1).Instead, novel gNB and UE implementations are utilized. For the case ofDL HARQ, the gNB scheduler is assumed to know, via OA&M configuration,which HARQ processes are used for TCP ACK. In this case, HARQ feedbackfor that HARQ processes is ignored by the gNB even if it is transmittedby the UE. UE ends up transmitting one or more acknowledgement bits, butthe overhead is small when compared to the overall size of uplinkcontrol information (UCI) (considering HARQ ACK/NCK for otherprocesses+CSI feedback). A similar concept is applicable for UL HARQACK/NACK for Autonomous Uplink (AUL) Physical Uplink Shared Channel(PUSCH).

Another solution, which will now be described, includes changing the MACfunctioning such that HARQ process ID does not get assigned toidentified Transport Blocks (TBs) for which HARQ ACK/NACK is to bedisabled. Two alternative designs are described below.

In a first alternative approach, a new dedicated HARQ process, similarto broadcast HARQ process, different to the HARQ processes available toMAC layer, is used. At the MAC layer, the MAC HARQ entity directs HARQinformation and associated TBs received on the DL-SCH to thecorresponding HARQ processes (NR uses 16 HARQ processes). Each time a TBis successfully decided, the MAC instructs the physical layer togenerate acknowledgments(s) of the data in the TB, unless it is abroadcast transmission (which is mapped to broadcast HARQ process), orif the timing alignment time has expired. In accordance with a featureof some embodiments, a new HARQ process category id is defined and usedfor such flows for which suppression of ACK/NACK is desired, which alsodoes not trigger generation of AC/NACK at the physical layer, similar tothe broadcast HARQ process [captured in TS 38.321].

In a second alternative approach, existing HARQ processes arere-purposed. New Radio (NR) allows the use of up to 16 HARQ processes.In some exemplary embodiments, of the present invention, the followingare included: (i) K HARQ process IDs are designated to be used to mean“No HARQ ACK/NAK” expected for the given TB(s) such that K is controlledby a new 4-bit RRC IE ‘HARQ Process ID for HARQ Suppression’; ii) a new4-bit RRC IE ‘HARQ Process ID for HARQ Suppression in DL’ is used toindicate which HARQ process IDs are to be used for TB(s) received in DLdirection which do not require HARQ feedback to sender; and iii) a new4-bit RRC IE ‘HARQ Process ID for HARQ Suppression in UL’ is used toindicate which HARQ process IDs are to be used in UL direction for TB(s)identified to not require HARQ feedback from receiver.

FIG. 6 is a drawing of an exemplary user equipment (UE) device 600 inaccordance with an exemplary embodiment. UE device 600 includes aprocessor 602, a wireless interface 604, a network interface 610, an I/Ointerface 616, an assembly of hardware components 616, e.g., an assemblyof circuits, and memory 620 coupled together via a bus 622 over whichthe various elements may interchange data and information. Wirelessinterface 604 includes a wireless receiver 638 coupled to receiveantenna 639, via which the UE may receive wireless signals, e.g.,wireless downlink signals from a base station, e.g., a gNB. Wirelessinterface 604 includes a wireless transmitter 640 coupled to transmitantenna 641, via which the UE may transmit wireless signals, e.g.,wireless uplink signals to a base station, e.g., a gNB. Networkinterface 610, e.g., a wired or optical interface 610 includes areceiver 678 and a transmitter 680.

UE device 600 further includes a microphone 624, a speaker 626, switches628, a mouse 634, a keypad 632, a display 630 and a camera 636 coupledto I/O interface 616, via which the various input/output devices (624,626, 628, 630, 632, 634, 636) may communicate with the other elements(602, 604, 610, 618, 620) of the UE device.

Memory 620 includes a control routine 652, an assembly of components654, e.g., an assembly of software components, a TCP component 667, TCPdata/information 677, an IP component 666, IP data/information 676, anRRC component 664, RRC data/information 674, an SDAP component 665, SDAPdata/information 675, a PDPC component 663, PDPC data/information 673,an RLC component 662, RLC data/information 672, a MAC component 661, MACdata/information 671, a PHY component 660, PHY data/information 670.

In some embodiments, UE device 600 includes one or more or all ofassembly of components 1400 of FIG. 14, assembly of components 1700 ofFIG. 17, assembly of components 2000 of FIG. 20, and assembly ofcomponents 2400 of FIG. 24.

FIG. 7 is a drawing of an exemplary base station 700, e.g., a gNB oreNB, in accordance with an exemplary embodiment. Base station 700includes a processor 702, a wireless interface 704, a network interface706, an assembly of hardware components 708, e.g., an assembly ofcircuits, and memory 710 coupled together via a bus 711 over which thevarious elements may interchange data and information. Wirelessinterface 704 includes a wireless receiver 712 coupled to receiveantenna 713, via which the base station 700 may receive wirelesssignals, e.g., wireless uplink signals from a UE device. Wirelessinterface 704 further includes a wireless transmitter 714 coupled totransmit antenna 715, via which the base station may transmit wirelesssignals, e.g., wireless downlink signals to a UE device. Networkinterface 706, e.g., a wired or optical interface 610 includes areceiver 716 and a transmitter 718.

Memory 710 includes a control routine 720, an assembly of components722, e.g., an assembly of software components, a TCP component 767, TCPdata/information 777, an IP component 766, IP data/information 776, anRRC component 765, RRC data/information 774, an SDAP component 765, SDAPdata/information 775, a PDPC component 763, PDPC data/information 773,an RLC component 762, RLC data/information 772, a MAC component 761, MACdata/information 771, a PHY component 760, PHY data/information 770.

In some embodiments, base station 700 includes one or more or all ofassembly of components 1300 of FIG. 13, assembly of components 1600 ofFIG. 16, assembly of components 1900 of FIG. 19, assembly of components2200 of FIG. 22, and assembly of components 2400 of FIG. 24.

FIG. 8 is a drawing of an exemplary server 800, e.g., an ApplicationServer (AS), in accordance with an exemplary embodiment. Server 800includes a processor 802, a network interface 804, an input device 806,e.g., a keyboard, an output device 808, e.g., a display, an assembly ofhardware components 810, e.g., an assembly of circuits, and memory 812coupled together via a bus 814 over which the various elements mayinterchange data and information. Network interface 804, e.g., a wiredor optical interface, includes a receiver 816 and a transmitter 818, viawhich server 800 may communicate with other devices, e.g., a basestation, a core network element, etc., via a backhaul network.

Memory 812 includes a control routine 820, an assembly of components822, e.g., an assembly of software components, a TCP component 830, TCPdata/information 838, an IP component 828, IP data/information 836,layer 2 components 826, layer 2 data/information 834, layer 1 components824, and layer 1 data/information 832.

FIG. 9 is a flowchart 900 of an exemplary method of operating acommunications system, e.g., a communications system including a basestation, e.g., a gNB or eNB, and a user equipment (UE) device, todisable Hybrid Automatic Repeat Request (HARQ) and/or Radio Link Control(RLC) ACKs for an identified traffic flow, e.g., a identified TCPtraffic flow supporting ACK which satisfies an additional servicecriteria, e.g., Quality Control Indicator (QCI)/5QI indicatingultra-reliable low latency communication (URLLC) in downlink inaccordance with an exemplary embodiment. Operation starts in step 902 inwhich the communications system is powered on and initialized. Operationproceeds from start step 902 to step 904.

In step 904, the base station is operated to monitor downlink packets tobe transmitted to the UE. Step 904 is performed on an ongoing basis.Step 904 includes step 906, in which the base station is operated todetect that a given packet is a TCP packet and satisfies any additionalservice criteria, e.g., QCI/5QI indicating URLLC packets. Operationproceeds from step 906 to step 908.

In step 908, the base station is operated to dynamically disable HARQand/or RLC ACKs for the sender of such packet prior to transmission.Operation proceeds from step 908 to step 910.

In step 910, the UE, which is to receive the TCP packet, is operated tochange its behavior to account for the dynamically disabled HARQ and/orRLC ACKs.

FIG. 10 is a flowchart 1000 of an exemplary method of operating acommunications system, e.g., a communications system including a basestation, e.g., a gNB or eNB, and a user equipment (UE) device, todisable Hybrid Automatic Repeat Request (HARQ) and/or Radio Link Control(RLC) ACKs for an identified traffic flow, e.g., a identified TCPtraffic flow supporting ACK which satisfies an additional servicecriteria, e.g., Quality Control Indicator (QCI)/5QI indicatingultra-reliable low latency communication (URLLC) in uplink in accordancewith an exemplary embodiment. Operation starts in step 1002 in which thecommunications system is powered on and initialized. Operation proceedsfrom start step 1002 to step 1004.

In step 1004, the UE is operated to monitor uplink packets to betransmitted to the base station. Step 1004 is performed on an ongoingbasis. Step 1004 includes step 1006, in which the base station isoperated to detect that a given packet is a TCP packet and satisfies anyadditional service criteria, e.g., QCI/5QI indicating URLLC packets.Operation proceeds from step 1006 to step 1008.

In step 1008, the UE is operated to dynamically disable HARQ and/or RLCacks for the sender of such packet prior to transmission. Operationproceeds from step 1008 to step 1010.

In step 1010, the base station, which is to receive the TCP packet, isoperated to change its behavior to account for the dynamically disabledHARQ and/or RLC ACKs.

FIG. 11 is a flowchart 1100 of an exemplary method of operating a UEdevice in a communications system, e.g., a new radio (NR) or LTEcommunications system supporting selective disabling of HARQ ACK/NACK,e.g., for identified TCP downlink traffic flows, satisfyingpredetermined criteria, in accordance with an exemplary embodiment.Operation starts in step 1102 in which the UE is powered on andinitialized. Operation proceeds from start step 1102 to step 1103.

In step 1103 the UE is operated to receive a SPS HARQ Off indicator in aSemi-Persistent Scheduling (SPS) Configuration (‘SPS-Config’)information element (IE) of a configuration message, said SPS HARQ OffIndicator being set to indicate that HARQ is not required. In someembodiments, the SPS HARQ Off Indicator is a 1 bit indicator. Operationproceeds from step 1103 to step 1104.

In step 1104 the UE is operated to receive a downlink controlinformation messages, e.g., a scheduling message, in DCI format 1_0 (forTDD) or DCI format 1_1 (for FDD) for C-RNTI or CS-RNTI, said DCI controlinformation message including a HARQ Off Indicator. In some embodiments,the HARQ Off Indicator is a 1 bit indicator. Operation proceeds fromstep 1104 to step 1106.

In step 1106, if the HARQ Off Indicator is set, then operation proceedsfrom step 1106 to step 1108. In step 1108 the UE ignores the HARQprocess number field and Physical Downlink Shared Channel(PDSCH)-to-HARQ feedback timing indicator field in the received downlinkcontrol information message communicating the received HARQ OffIndicator value. Step 1108 causes the UE to refrain from transmitting aHARQ ACK/NACK corresponding to the communicated downlink trafficscheduled by the downlink control information of step 1104.

In step 1106, if the HARQ Off Indicator is not set, e.g., value=0, thenoperation proceeds from step 1106 to step 1110 in which the UE usesvalues in the HARQ process number field and PDSCH-to-HARQ feedbacktiming indicator field in the received downlink control informationmessage communicating the received HARQ Off Indicator value to performnormal HARQ acknowledgement processing.

Operation proceeds from step 1108 or step 1110 via connecting node A1112 to step 1104.

FIG. 12 is a flowchart 1200 of an exemplary method of operating acommunications system in accordance with an exemplary embodiment, saidcommunications system including a first wireless communications deviceincluding a transmitter. In various embodiments, the communicationssystem includes a second wireless communications device. In someembodiments, the first wireless communications device is a base station,e.g., a gNB or an eNB, and the second wireless communications device isa user equipment device (UE), said base station and said UE deviceimplemented in accordance with various features and/or aspects of thepresent invention. In some other embodiments, the first wirelesscommunications device is a user equipment device (UE), and secondwireless communications device is a base station, e.g., a gNB or an eNB,and, said UE device and said base station implemented in accordance withvarious features and/or aspects of the present invention. Operationstarts in step 1202 in which the communications system is powered on andinitialized. Operation proceeds from start step 1202 to step 1204.

In step 1204, the first wireless communications device identifies, atthe first wireless communications device, a first traffic flow. Step1204 includes step 1206 in which the first wireless communicationsdevice identifies a first traffic flow that supports an end to endre-transmission method in the event of a communications failure of databeing communicated. Operation proceeds from step 1204 to step 1208.

In step 1208 the first wireless communications device transmits, fromthe first wireless communications device, an explicit indication to thesecond wireless communications device to skip Hybrid Automatic RepeatRequest (HARQ) feedback for data, corresponding to the first trafficflow, said data being transmitted to the second wireless communicationsdevice. Step 1208 includes step 1210 or step 1212, depending upon theexemplary embodiment. Step 1210 is included for an embodiment in whichthe first wireless communications device is a base station, e.g., afirst base station; the second wireless communications device, e.g., aUE, is a device which includes a wireless receiver for receiving datafrom the first base station; and the first traffic flow is a downlinktraffic flow. Step 1212 is included for an embodiment in which the firstwireless communications device, e.g., a UE, includes a transmitter fortransmitting to a base station; the second wireless communicationsdevice is a base station which includes a wireless receiver forreceiving data from the first wireless communications device, e.g., theUE; and the first traffic flow is an uplink traffic flow.

In step 1210 the first wireless communications device, which is a basestation, e.g., a gNB or eNB, transmits a Semi-Persistent Scheduling(SPS) HARQ Off Indicator set to indicate that HARQ is disabled in aradio configuration information element, e.g., in radio resource control(RRC) information element (IE) ‘SPS-Config’. In some embodiments, theSPS HARQ Off Indicator is a one bit value set to a predetermined value,e.g., 1, when HARQ is disabled. Operation proceeds from step 1210 tostep 1214.

In step 1214 the first wireless communications device, which is a basestation, transmits from the first wireless communications device to thesecond wireless communications device, a HARQ Off Indicator, set toindicate HARQ is disabled, said HARQ Off Indicator being transmitted ina downlink control information (DCI) format, e .g., DCI format 1_0 orDCI format 1_1, scheduling message. In some embodiments, the HARQ OffIndicator is a one bit value set to a predetermined value, e.g., 1, whenHARQ is disabled. Operation proceeds from step 1214 to step 1216.

In step 1216 the second wireless communications device, which is a UE,is operated to ignore at least one of: i) information in a PhysicalDownlink Shared Channel (PDSCH)-to-HARQ feedback timing indicator fieldor ii) information in a HARQ process number field of downlink controlinformation provided by the first wireless communications device withrespect to the first traffic flow.

Returning to step 1212, in step 1212, the first wireless communicationsdevice, which is a UE device, transmits an Autonomous Uplink (AUL) HARQOff Indicator to the second wireless communications device, which is abase station. In various embodiments, the AUL HARQ Off Indicator is aone bit value set to a value indicating that HARQ is disabled withrespect to the first traffic flow, e.g., AUL HARQ Off Indicator=1indicates HARQ is disabled with respect to the first traffic flow.

Operation proceeds from step 1212 to step 1218. In step 1218, the secondwireless communications device, which is a base station, is operated torefrain from transmitting an uplink HARQ acknowledgment/negativeacknowledgment (ACK/NACK) with respect to autonomous uplink transmissionwith regard to the first traffic flow.

Operation proceeds from step 1216 or step 1218 to step 1220. In step1220 the first wireless communications device, identifies at the firstwireless communications device, a second traffic flow, said secondtraffic flow being a traffic flow which does not support an end to endre-transmission method. Operation proceeds from step 1220 to step 1222.In step 1222 the first wireless communications device is operated totransmit data to the second wireless communications device withoutdisabling HARQ feedback for the second traffic flow.

FIG. 13 is a drawing of an exemplary assembly of components 1300 whichmay be included in a wireless communications device, e.g., a basestation such as the exemplary base station 700 of FIG. 7, and implementsteps of an exemplary method, e.g., steps of the method of the flowchart1200 of FIG. 12.

Assembly of components 1300 can be, and in some embodiments is, used inbase station 700, e.g., a gNB or eNB, of FIG. 7 or base station 406 orbase station 408 of FIG. 4. The components in the assembly of components1300 can, and in some embodiments are, implemented fully in hardwarewithin the processor 702, e.g., as individual circuits. The componentsin the assembly of components 1300 can, and in some embodiments are,implemented fully in hardware within the assembly of components 708,e.g., as individual circuits corresponding to the different components.In other embodiments some of the components are implemented, e.g., ascircuits, within the processor 702 with other components beingimplemented, e.g., as circuits within assembly of components 708,external to and coupled to the processor 702. As should be appreciatedthe level of integration of components on the processor and/or with somecomponents being external to the processor may be one of design choice.Alternatively, rather than being implemented as circuits, all or some ofthe components may be implemented in software and stored in the memory710 of the base station 700, e.g., a gNB or eNB, with the componentscontrolling operation of the base station to implement the functionscorresponding to the components when the components are executed by aprocessor, e.g., processor 702. In some such embodiments, the assemblyof components 1300 is included in the memory 710 as assembly ofcomponents 722. In still other embodiments, various components inassembly of components 1300 are implemented as a combination of hardwareand software, e.g., with another circuit external to the processorproviding input to the processor 702 which then under software controloperates to perform a portion of a component's function. While processor702 is shown in the FIG. 7 embodiment as a single processor, e.g.,computer, it should be appreciated that the processor 702 may beimplemented as one or more processors, e.g., computers.

When implemented in software the components include code, which whenexecuted by the processor 702, configure the processor 702 to implementthe function corresponding to the component. In embodiments where theassembly of components 1300 is stored in the memory 710, the memory 710is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each component, for causingat least one computer, e.g., processor 702, to implement the functionsto which the components correspond.

Completely hardware based or completely software based components may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented components may be used toimplement the functions. As should be appreciated, the componentsillustrated in FIG. 13 control and/or configure the base station 700, orelements therein such as the processor 702, to perform the functions ofcorresponding steps illustrated and/or described in the method of one ormore of the flowcharts, signaling diagrams and/or described with respectto any of the Figures. Thus the assembly of components 1300 includesvarious components that perform functions of corresponding one or moredescribed and/or illustrated steps of an exemplary method, e.g., stepsof the method of flowchart 1200 of FIG. 12 and/or described or shownwith respect to any of the other figures.

Assembly of components 1300 includes a component 1204 configured toidentify at the base station a first traffic flow, e.g., a firstdownlink traffic flow. Component 1304 includes a component 1306configured to identify a first traffic flow, e.g., a first downlinktraffic flow that supports end to end retransmission method in the eventof a communications failure of data being communicated. Assembly ofcomponents 1300 further includes a component 1308 configured to controlthe base station to transmit an explicit indication to a second wirelesscommunications device to skip Hybrid Automatic Repeat Request (HARQ)feedback for data, corresponding to the first traffic flow, said databeing transmitted to the second wireless communications device.Component 1308 includes a component 1310 configured to control the basestation to transmit a semi-persistent scheduling (SPS) HARQ OffIndicator set to indicate that HARQ is disabled, said SPS HARQ OffIndicator being sent in a radio configuration information element, saidsecond wireless communications device being a user equipment (UE)device. In some embodiments, the SPS HARQ Off indicator is a one bitvalue set to a predetermined value, e.g., 1, when HARQ is disabled.

Assembly of components 1300 further includes a component 1314 configuredto control the base station to transmit, from the base station to thesecond wireless communications device, a HARQ Off Indicator set toindicate that HARQ is disabled, as HARQ Off Indicator being transmittedin a downlink control information format scheduling message. In someembodiments, the HARQ Off Indicator is a one bit value set to apredetermined value, e.g., 1, when HARQ is disabled. In someembodiments, the DCI format is one of a DCI format 1_0 or a DCI format1_1.

Assembly of components 1300 further includes a component 1320 configuredto identify, at the base station, a second traffic flow, said secondtraffic flow being a traffic flow which does not support an end to endretransmission method, a component 1322 configured to control the basestation to transmit data to the second wireless communications devicewithout disabling HARQ feedback for the second traffic flow, and acomponent 1318 configured to control the base station to refrain fromtransmitting an uplink HARQ acknowledgment/negative acknowledgment(ACK/NACK) with respect to autonomous uplink transmission with regard toa first uplink traffic flow.

FIG. 14 is a drawing of an exemplary assembly of components 1400 whichmay be included in a wireless communications device, e.g., a UE such asthe UE 600 of FIG. 6, and implement steps of an exemplary method, e.g.,steps of the method of the flowchart 1200 of FIG. 12.

Assembly of components 1400 can be, and in some embodiments is, used inUE device 600 of FIG. 6 or UE 402 or UE 404 of FIG. 4. The components inthe assembly of components 1400 can, and in some embodiments are,implemented fully in hardware within the processor 602, e.g., asindividual circuits. The components in the assembly of components 1400can, and in some embodiments are, implemented fully in hardware withinthe assembly of components 618, e.g., as individual circuitscorresponding to the different components. In other embodiments some ofthe components are implemented, e.g., as circuits, within the processor602 with other components being implemented, e.g., as circuits withinassembly of components 618, external to and coupled to the processor602. As should be appreciated the level of integration of components onthe processor and/or with some components being external to theprocessor may be one of design choice. Alternatively, rather than beingimplemented as circuits, all or some of the components may beimplemented in software and stored in the memory 620 of the UE 600, withthe components controlling operation of the UE 600 to implement thefunctions corresponding to the components when the components areexecuted by a processor, e.g., processor 602. In some such embodiments,the assembly of components 1400 is included in the memory 620 asassembly of components 654. In still other embodiments, variouscomponents in assembly of components 1400 are implemented as acombination of hardware and software, e.g., with another circuitexternal to the processor providing input to the processor 602 whichthen under software control operates to perform a portion of acomponent's function. While processor 602 is shown in the FIG. 6embodiment as a single processor, e.g., computer, it should beappreciated that the processor 602 may be implemented as one or moreprocessors, e.g., computers.

When implemented in software the components include code, which whenexecuted by the processor 602, configure the processor 602 to implementthe function corresponding to the component. In embodiments where theassembly of components 1400 is stored in the memory 620, the memory 620is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each component, for causingat least one computer, e.g., processor 602, to implement the functionsto which the components correspond.

Completely hardware based or completely software based components may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented components may be used toimplement the functions. As should be appreciated, the componentsillustrated in FIG. 14 control and/or configure the UE 600, or elementstherein such as the processor 602, to perform the functions ofcorresponding steps illustrated and/or described in the method of one ormore of the flowcharts, signaling diagrams and/or described with respectto any of the Figures. Thus the assembly of components 1400 includesvarious components that perform functions of corresponding one or moredescribed and/or illustrated steps of an exemplary method, e.g., stepsof the method of flowchart 1200 of FIG. 12 and/or described or shownwith respect to any of the other figures.

Assembly of components 1400 includes a component 1404 configured toidentify at the UE device, a first traffic flow, e.g., a first uplinktraffic flow. Component 1404 includes a component 1406 configured toidentify a first traffic flow, e.g., a first uplink traffic flow, thatsupports an end to end retransmission method in the event of acommunications failure of data being communicated. Assembly ofcomponents 1400 further includes a component 1408 configured to controlthe UE to transmit an explicit indication to a second wirelesscommunications device, e.g., a base station such as a gNB or eNB, toskip Hybrid Automatic Repeat Request (HARQ) feedback for data,corresponding to the first traffic flow, e.g., a first uplink trafficflow, said data being communicated to the second wireless device.Component 1408 includes a component 1412 configured to control the UE totransmit an automatic uplink (AUL) HARQ Off Indicator to the secondwireless communications device, said second wireless communicationsdevice being a base station, e.g., a gNB or eNB. In some embodiments,assembly of components includes a component 1413 configured to control atransmitter in the UE device to transmit autonomous uplink-uplinkcontrol information (AUL-UCI) that accompanies an autonomousuplink-physical uplink shared channel (AUL-PUSCH) corresponding to saidfirst traffic flow, said AUL-UCI including an AUL HARQ Off Indicator. Insome embodiments, component 1413 includes component 1212. In someembodiments the automatic uplink HARQ Off Indicator is referred to as anautonomous uplink HARQ Off Indicator.

In some embodiments, the AUL HARQ Off Indicator is a one bit indicator.In some such embodiments, when the value of the AUL HARQ Off Indicatoris set to 1, the AUL HARQ Off Indicator indicates that the HARQ isdisabled with respect to the first traffic flow, and when the value ofthe AUL HARQ Off Indicator is set to 0, the AUL HARQ Off indicatorindicates that HARQ is enabled with respect to the first traffic flow.

Assembly of components 1400 further includes a component 1420 configuredto identify, at the UE device, a second traffic flow, said secondtraffic flow being a traffic flow which does not support an end to endretransmission method, a component 1422 configured to control the UE totransmit data to the second wireless communications device withoutdisabling HARQ feedback for the second traffic flow, an a component 1416configured to operate the UE to ignore at least one of: i) informationin a physical downlink shared channel (PDSCH)-to-HARQ Feedback Timingfield or ii) information in a HARQ process number field of downlinkcontrol information provided by a first wireless communications device,e.g., a base station, with respect to a first traffic flow, e.g., afirst downlink traffic flow.

FIG. 15 is a flowchart 1500 of an exemplary method of operating a firstcommunications device including a transmitter in accordance with variousexemplary embodiments. In some exemplary embodiments, the firstcommunications device is a base station, e.g., a gNB or an eNB. In someother embodiments, the first communications device is a user equipment(UE) device. Operation starts in step 1502 in which the firstcommunications device is powered on and initialized. Operation proceedsfrom step 1502 to step 1504, in which the first communications deviceidentifies a first packet flow for which end to end retransmission ofpackets is supported. Step 1504 includes step 1506 in which the firstcommunications device identifies a first packet flow for which end toend retransmission of packets is supported and for which HybridAutomatic Repeat Request (HARQ) is to be suppressed, e.g., a TCP packetflow supporting ACK which meets certain criteria, e.g., QCI/5QIindicating ultra-reliable low latency communications (URLLC) packets oranother criteria. In some embodiments, e.g., some embodiments in whichsome of the HARQ processes are dedicated to be no ACK/NACK expectedprocesses, operation proceeds from step 1504 to step 1518. In otherembodiments, e.g., some embodiments in which the first communicationsdevice can, and sometimes does, repurpose, e.g., dynamically repurpose,HARQ processes, operation proceeds from step 1504 to step 1508.

In step 1508, the first communications device designates K HybridAutomatic Repeat Request (HARQ) process IDs, corresponding to K HARQprocesses, said K HARQ process IDs being used to mean no ACK/NACKexpected, said K HARQ processes to be used for Transport Blocks (TBs) onwhich HARQ is to be suppressed. Operation proceeds from step 1508 tostep 1510.

In step 1510 the first communications device generates a radio resourcecontrol (RRC) message including a RRC information element (IE), e.g., a4 bit IE, identifying the K HARQ processes designated as No ACK/NACKexpected. In some embodiments, RRC information element (IE) identifyingthe K HARQ processes designated as a No ACK/NACK expected, is a four bitinformation element.

In some such embodiments, K is an integer in the range of {0 . . . 15}.In some such embodiments, K is an integer in the range of {1 . . . 15}.In some such embodiments, K is an integer in the range of {1 . . . 16}.

In some embodiments, the first communications is a base station, e.g., agNB or eNB, the first packet flow is a downlink packet flow, and step1510 includes step 1512. In step 1512 the first communications devicegenerates a radio resource control message including an RRC IE ‘HARQprocess ID for suppression in DL’, which communicates a value indicatingwhich HARQ process IDs are to be used for TBs received in the downlinkdirection which do not require HARQ feedback to the sender. In someembodiments, the RRC IE ‘HARQ process ID for HARQ SUPPRESSION in DL’ isa four bit information element. In some such embodiments, step 1512includes step 1513 in which the first communications device includes insaid RRC message an RRC IE ‘HARQ process ID for HARQ SUPPRESSION’including a value indicating the K number of HARQ processes designatedas No HARQ ACK/NACK expected. In some embodiments, the RRC IE ‘HARQprocess ID for HARQ SUPPRESSION’ is a four bit information element.

In some embodiments, the first communications is a UE, the first packetflow is an uplink packet flow, and step 1510 includes step 1514. In step1514 the first communications device generates a radio resource controlmessage including an RRC IE ‘HARQ process ID for suppression in UL’,which communicates a value indicating which HARQ process IDs are to beused in the uplink direction for TBs identified to not require HARQfeedback from receiver. In some such embodiments, step 1514 includesstep 1515 in which the first communications device includes in said RRCmessage an RRC IE ‘HARQ process ID for HARQ SUPPRESSION’ including avalue indicating the K number of HARQ processes designated as No HARQACK/NACK expected. In some embodiments, the RRC IE ‘HARQ process ID forHARQ SUPPRESSION’ is a four bit information element.

In some embodiments the value communicated in the RRC IE ‘HARQ processID for HARQ SUPPRESSION’ communicates the number K, and the valuecommunicated in the RRC IE ‘HARQ process ID for HARQ SUPPRESSION in DL’identified a specific set of K HARQ processes, each HARQ processassociated with a HARQ process ID.

For example, in some embodiments, when K=4, and HARQ process with IDs 0,1, 2, and 3 are designated as a No ACK/NACK expected, the RRC IE ‘HARQprocess ID for HARQ SUPPRESSION’ communicates a value, e.g., 4, whichindicates that K=4, and the RRC IE ‘HARQ process ID for HARQ SUPPRESSIONin DL’ communicates that a value 1, which indicates that HARQ processwith IDs 0, 1, 2, and 3 are designated as a No ACK/NACK expected.Continuing with the example, in some embodiments, when K=4, and HARQprocess with IDs 16, 15, 14, and 13 are designated as a No ACK/NACKexpected, the RRC IE ‘HARQ process ID for HARQ SUPPRESSION’ communicatesa value, e.g., 4, which indicates that K=4, and the RRC IE ‘HARQ processID for HARQ SUPPRESSION in DL’ communicates that a value 2, whichindicates that HARQ process with IDs 16, 15, 14, and 13 are designatedas a No ACK/NACK expected.

In some embodiments, in the RRC message, there is a single RRC IE ‘HARQprocess ID for HARQ SUPPRESSION’ communicating the value K, and thereare K instances of the RRC IE ‘HARQ process ID for HARQ SUPPRESSION inDL’, each of the K instances communicating an identifier of a HARQprocess which has been designated as a No HARQ ACK/NACK process.

In some embodiments the value communicated in the RRC IE ‘HARQ processID for HARQ SUPPRESSION’ communicates the number K, and the valuecommunicated in the RRC IE ‘HARQ process ID for HARQ SUPPRESSION in UL’identified a specific set of K HARQ processes, each HARQ processassociated with a HARQ process ID.

For example, in some embodiments, when K=5, and HARQ process with IDs 0,1, 2, 3 and 4 are designated as a No ACK/NACK expected, the RRC IE ‘HARQprocess ID for HARQ SUPPRESSION’ communicates a value, e.g., 5, whichindicates that K=5, and the RRC IE ‘HARQ process ID for HARQ SUPPRESSIONin DL’ communicates that a value 1, which indicates that HARQ processwith IDs 0, 1, 2, 3 and 4 are designated as a No ACK/NACK expected.Continuing with the example, in some embodiments, when K=5, and HARQprocess with IDs 16, 15, 14, 13 and 12 are designated as a No ACK/NACKexpected, the RRC IE ‘HARQ process ID for HARQ SUPPRESSION’ communicatesa value, e.g., 5, which indicates that K=5, and the RRC IE ‘HARQ processID for HARQ SUPPRESSION in DL’ communicates that a value 2, whichindicates that HARQ process with IDs 16, 15, 14, 13 and 12 aredesignated as a No ACK/NACK expected.

In some embodiments, in the RRC message, there is a single RRC IE ‘HARQprocess ID for HARQ SUPPRESSION’ communicating the value K, and thereare K instances of the RRC IE ‘HARQ process ID for HARQ SUPPRESSION inUL’, each of the K instances communicating an identifier of a HARQprocess which has been designated as a No HARQ ACK/NACK process.

Operation proceeds from step 1510 to step 1516, in which the firstcommunications device transmits said generated radio resource control(RRC) message, including a RCC information element (IE) identifying theK HARQ processes designated as no ACK/NACK expected, to said secondcommunications device. Operation proceeds from step 1516 to step 1518.

In step 1518 the first communications device assigns said first packetflow to a hybrid automatic repeat request (HARQ) process which does notrequire generation of acknowledgment (ACKs) or negative acknowledgment(NACKs) from a device receiving data corresponding to said first packetflow.

In some embodiments, the HARQ process is a HARQ process for a TCP packetflow which supports end to end retransmission of packets, said HARQprocess not supporting retransmission of data in response to a NACK andnot requiring transmission of ACKs/NACKs from the receiving device towhich data was transmitted. In some such embodiments, e.g., someembodiments in which steps 1508, 1510 and 1516 are bypassed, said HARQprocess assigned in step 1518 is a dedicated HARQ process for a flow forwhich suppression of ACK/NACK is required, said dedicated HARQ processfor the flow not triggering generation of ACK/NACK at the physicallayer.

In some embodiments, e.g., some embodiments in which steps 1508, 1510and 1516 are performed, the HARQ process assigned in step 1518 is one ofthe K designated HARQ processes of step 1508.

Step 1518 includes step 1520 in which the first communications deviceassigns said first packet flow to a HARQ process ID which is designatedas indicating a HARQ suppression. In some embodiments, the HARQ processID for the first packet flow is communicated in a Radio Resource Controlinformation Element (RRC IE). In some embodiments, the HARQ Process IDis a 4 bit ID.

In some embodiments, the first communications device is a base stationand the second communications device is a UE and the RRC IE indicates aHARQ process to be used for a corresponding transmission block (TB)transmitted in the downlink channel.

In some embodiments, the first communications device is a UE and thesecond communications device is a base station and the HARQ process towhich the first packet flow is assigned is to be used for acorresponding uplink (UL) transmission block (TB) transmitted in anuplink channel.

In some embodiments, e.g., some embodiments, in which the firstcommunications device is a base station and the first packet flow is adownlink packet flow, operation proceeds from step 1518 to step 1522. Insome other embodiments, e.g., some embodiments, in which the firstcommunications device is a UE device and the first packet flow is anuplink packet flow, operation proceeds from step 1518 to step 1526.

In step 1522 the first communications device transmits said HARQ processID for the first packet flow to the second communications device. Step1522 includes step 1524 in which the first communications devicetransmits said HARQ process ID for the first packet flow to secondcommunications device in an information element (IE) of a physicaldownlink control channel (PDCCH). In some embodiments the IE of thePDCCH is a Radio Resource Control (RRC) IE, e.g., of a RCC message.Operation proceeds from step 1522 to step 1526.

In step 1526, the first communications device transmits datacorresponding to said first packet flow to the second communicationsdevice.

In some embodiments, in step 1526, the first communications device is abase station, which transmits data corresponding to said first packetflow to the second communications device, which is a UE, which includesa receiver, and the second communications device is one end of the firstpacket flow, and the first packet flow has another endpoint, which is athird communications device, e.g., another UE or a server, e.g., anapplication server.

In some embodiments, in step 1526, the first communications device is aUE, which transmits data corresponding to said first packet flow to thesecond communications device, which is a base station, which includes areceiver, and the second communications device is an intermediary pointof the first packet flow, and the first packet flow has anotherendpoint, which is a third communications device, e.g., another UE or aserver, e.g., an application server.

In some embodiments, in which the first communications device is a UE,different uplink transmission slots are mapped to different known HARQprocess IDs, and the mapping is known the base station and the UE.Therefore the base station can determine the HARQ process IDcorresponding to the received packets of the first packet flow, andbased on predetermined known information or received information as towhich HARQ IDs correspond to a no HARQ ACK/NACK designation, the basestation is able to determine that the first packet flow packetscorresponds to no HARQ ACK/NACK, since the UE has transmitted the datapackets in a slot corresponding to an HARQ ID which is designated as noACK/NACK required, sometimes alternatively referred to as No ACK/NACKexpected or No ACK/NACK suppression.

Operation proceeds from step 1526 to step 1528. In step 1528 the firstcommunications device identifies a second packet flow, said secondpacket flow being a packet flow which does not support and end to endretransmission method. Operation proceeds from step 1528 to step 1530.In step 1530 the first communications device transmits data to thesecond communications device without disabling HARQ feedback for thesecond packet flow.

FIG. 16 is a drawing of an exemplary assembly of components 1600 whichmay be included in a wireless communications device, e.g., a basestation such as the exemplary base station 700, e.g. a fNB or eNB, ofFIG. 7, and implement steps of an exemplary method, e.g., steps of themethod of the flowchart 1500 of FIG. 15.

Assembly of components 1600 can be, and in some embodiments is, used inbase station 700, e.g., a gNB or eNB, of FIG. 7 or base station 406 orbase station 408 of FIG. 4. The components in the assembly of components1600 can, and in some embodiments are, implemented fully in hardwarewithin the processor 702, e.g., as individual circuits. The componentsin the assembly of components 1600 can, and in some embodiments are,implemented fully in hardware within the assembly of components 708,e.g., as individual circuits corresponding to the different components.In other embodiments some of the components are implemented, e.g., ascircuits, within the processor 702 with other components beingimplemented, e.g., as circuits within assembly of components 708,external to and coupled to the processor 702. As should be appreciatedthe level of integration of components on the processor and/or with somecomponents being external to the processor may be one of design choice.Alternatively, rather than being implemented as circuits, all or some ofthe components may be implemented in software and stored in the memory710 of the base station 700, e.g., a gNB or eNB, with the componentscontrolling operation of the base station to implement the functionscorresponding to the components when the components are executed by aprocessor, e.g., processor 702. In some such embodiments, the assemblyof components 1600 is included in the memory 710 as assembly ofcomponents 722. In still other embodiments, various components inassembly of components 1600 are implemented as a combination of hardwareand software, e.g., with another circuit external to the processorproviding input to the processor 702 which then under software controloperates to perform a portion of a component's function. While processor702 is shown in the FIG. 7 embodiment as a single processor, e.g.,computer, it should be appreciated that the processor 702 may beimplemented as one or more processors, e.g., computers.

When implemented in software the components include code, which whenexecuted by the processor 702, configure the processor 702 to implementthe function corresponding to the component. In embodiments where theassembly of components 1600 is stored in the memory 710, the memory 710is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each component, for causingat least one computer, e.g., processor 702, to implement the functionsto which the components correspond.

Completely hardware based or completely software based components may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented components may be used toimplement the functions. As should be appreciated, the componentsillustrated in FIG. 16 control and/or configure the base station 700, orelements therein such as the processor 702, to perform the functions ofcorresponding steps illustrated and/or described in the method of one ormore of the flowcharts, signaling diagrams and/or described with respectto any of the Figures. Thus the assembly of components 1600 includesvarious components that perform functions of corresponding one or moredescribed and/or illustrated steps of an exemplary method, e.g., stepsof the method of flowchart 1500 of FIG. 15 and/or described or shownwith respect to any of the other figures.

FIG. 16 is a drawing of an assembly of components 1600 including acomponent 1604 configured to identify a first packet flow for which endto end transmission of packets is supported. Component 1604 includes acomponent 1606 configured to identify a first packet flow for which endto end retransmission of packets is supported and which HARQ is to besuppressed. Assembly of components 1600 further includes a component1608 configured to designate K Hybrid automatic retransmission request(HARQ) process IDs corresponding to K HARQ processes to be used to meanno ACK/ACK expected, said K HARQ processes to be used for transportblocks (TBs) on which HARQ is to be suppressed, and a component 1610configured to generate a radio resource control RRC message indicating aRRC information element (IE), e.g., a 4 bit IE, identifying the K HARQprocesses designated as no ACK/NACK expected. Component 1610 includes acomponent configured to generate a RRC message including a RRC IE ‘HARQProcess ID for Suppression in DL’ which communicates a value indicatingwhich HARQ Process IDs are to be used for TBs received in the downlinkdirection which do not require HARQ feedback to send. Component 1612includes a component 1613 configured to include in said RRC message anRRC IE ‘HARQ Process ID for HARQ Suppression’ including a valueindicating the K number of HARQ processes designated as a No HARQACK/NACK expected.

Assembly of components 1600 further includes a component 1616 configuredto operate the base station to transmit said generated radio resourcecontrol (RRC) message, including a RRC information element (IE)identifying the K HARQ processes designated as no ACK/NACK expected, tosaid second communications device. In some embodiments, the RRC IEidentifying the K HARQ processes designated a No ACK/NACK expected is afour bit information element.

Assembly of components 1600 further includes a component 1618 configuredto assign said first packet flow to a Hybrid Automatic Repeat Request(HARQ) process which does not require generate of acknowledgments (ACKs)or negative acknowledgments (NACKs) from a device, e.g., a UE, receivingdata corresponding to said first packet flow. Component 1618 includes acomponent 1620 configured to assign said first packet flow to a HARQprocess ID which is designated as indicating a HARQ suppression. In someembodiments, some HARQ process ID(s) are dedicated for HARQ suppression.In some embodiments, some HARQ process IDs, e.g., K HARQ processes aretemporarily designated for HARQ suppression, e.g., with the value of Kchanging over time depending upon current conditions.

In some embodiments, the HARQ process to which the first packet flow isassigned is a HARQ process for a TCP packet flow which supports end toend retransmission of packets, said HARQ process not supportingretransmission of data in response to a NACK and not requiringtransmission of ACKs/NACKs from the receiving device to which data wastransmitted. In some such embodiments, the HARQ process to which thefirst packet flow is assigned is a dedicated HARQ process for a flow forwhich suppression of ACK/NACK is required, said dedicated HARQ processfor the flow not triggering generation of ACK/NACK at the physicallayer.

In various embodiments, the HARQ process ID for the first packet flow iscommunicated in a RRC IE (Radio Resource Control Information Element),e.g., a RRC IE of a Physical Downlink Control Channel (PDCCH), e.g., ofa RRC message. In some embodiments, the RRC IE indicates a HARQ processto be used for a corresponding transmission block (TB) in a downlinkchannel.

Assembly of components 1600 further includes a component 1622 configuredto control the base station to transmit the HARQ process ID for thefirst packet flow to the second communications device. Component 1622includes component 1624 configured to operate the base station totransmit the HARQ process ID for the first packet flow to the secondcommunications device in an information element (IE) of a physicaldownlink control channel (PDCCH). Assembly of components 1600 furtherincludes a component 1626 configured to operate the base station totransmit data corresponding to the first packet flow to a secondcommunication device, a component 1628 configured to identify a secondpacket flow, e.g., a second downlink packet flow, said second packetflow being a packet flow which does not support and end to endretransmission method, and a component 1630 configured to control thebase station to transmit data to the second communications device, e.g.,a UE, without disabling HARQ feedback for the second packet flow.

FIG. 17 is a drawing of an exemplary assembly of components which may beincluded in a wireless communications device, e.g., a UE such as the UE600 of FIG. 6, and implement steps of an exemplary method, e.g., stepsof the method of the flowchart 1500 of FIG. 15.

Assembly of components 1700 can be, and in some embodiments is, used inUE device 600 of FIG. 6 or UE 402 or UE 404 of FIG. 4. The components inthe assembly of components 1700 can, and in some embodiments are,implemented fully in hardware within the processor 602, e.g., asindividual circuits. The components in the assembly of components 1700can, and in some embodiments are, implemented fully in hardware withinthe assembly of components 618, e.g., as individual circuitscorresponding to the different components. In other embodiments some ofthe components are implemented, e.g., as circuits, within the processor602 with other components being implemented, e.g., as circuits withinassembly of components 618, external to and coupled to the processor602. As should be appreciated the level of integration of components onthe processor and/or with some components being external to theprocessor may be one of design choice. Alternatively, rather than beingimplemented as circuits, all or some of the components may beimplemented in software and stored in the memory 620 of the UE 600, withthe components controlling operation of the UE 600 to implement thefunctions corresponding to the components when the components areexecuted by a processor, e.g., processor 602. In some such embodiments,the assembly of components 1400 is included in the memory 620 asassembly of components 654. In still other embodiments, variouscomponents in assembly of components 1700 are implemented as acombination of hardware and software, e.g., with another circuitexternal to the processor providing input to the processor 602 whichthen under software control operates to perform a portion of acomponent's function. While processor 602 is shown in the FIG. 6embodiment as a single processor, e.g., computer, it should beappreciated that the processor 602 may be implemented as one or moreprocessors, e.g., computers.

When implemented in software the components include code, which whenexecuted by the processor 602, configure the processor 602 to implementthe function corresponding to the component. In embodiments where theassembly of components 1700 is stored in the memory 620, the memory 620is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each component, for causingat least one computer, e.g., processor 602, to implement the functionsto which the components correspond.

Completely hardware based or completely software based components may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented components may be used toimplement the functions. As should be appreciated, the componentsillustrated in FIG. 17 control and/or configure the UE 600, or elementstherein such as the processor 602, to perform the functions ofcorresponding steps illustrated and/or described in the method of one ormore of the flowcharts, signaling diagrams and/or described with respectto any of the Figures. Thus the assembly of components 1700 includesvarious components that perform functions of corresponding one or moredescribed and/or illustrated steps of an exemplary method, e.g., stepsof the method of flowchart 1500 of FIG. 15 and/or described or shownwith respect to any of the other figures.

Assembly of components 1700 includes a component 1704 configured toidentify a first packet flow for which end to end retransmission ofpackets is supported. Component 1704 includes a component 1706configured to identify a first packet flow for which HARQ is to besuppressed. Assembly of components 1700 further includes a component1708 configured to designate K Hybrid Automatic Repeat Request (HARQ)process IDs corresponding to K HARQ processes to be used to mean NoACK/NACK expected, said K HARQ processing to be used for TransportBlocks (TBs) on which HARQ is to be suppressed and a component 1710configured to generate a radio resource control (RRC) message includinga RRC information element (IE), e.g., a 4 IE, identifying the K HARQprocesses designated as no ACK/NACK expected. Component 1710 includes acomponent 1714 configured to generate a RRC message including an RRC IE,‘HARQ Process ID for Suppression in UL’, e.g., a 4 bit IE, whichcommunicates a value indicating which HARQ process IDs are to be usedfor the uplink direction for TBs identified to not require HARQ feedbackfrom receiver. Component 1714 includes a component 1715 configured toinclude in said RRC message an RRC IE, ‘HARQ process ID for HARQsuppression’, including a value indicating the K number of HARQprocesses designated as no HARQ ACK/NACK expected.

Assembly of components 1700 further includes a component 1716 configuredto operate the UE to transmit said generated radio resource control(RRC) message, including a RRC resource information element (IE)identifying the K HARQ processes designated as no ACK/NACK expected, tosaid second communications device, e.g., a base station, a component1718 configured to assign said first packet flow to a Hybrid AutomaticRepeat Request (HARQ) process which does not require generation ofacknowledgments (ACKs) or negative acknowledgments (NACKs) for a devicereceiving data corresponding to said first packet flow. Component 1718includes a component 1720 configured to assign said first packet flow toa HARQ process ID which is designated as indicating a HARQ suppression.

In some embodiments, some HARQ process ID(s) are dedicated for HARQsuppression. In some embodiments, some HARQ process IDs, e.g., K HARQprocess IDs, are temporarily designated for HARQ suppression, e.g., withthe value of K changing over time depending upon current conditions.

In some embodiments, the HARQ process to which the first packet flow isassigned is a HARQ process for a TCP packet flow which supports end toend retransmission of packets, said HARQ process not supportingretransmission of data in response to a NACK and not requiringtransmission of ACKs/NACKs from the receiving device to which data wastransmitted. In some such embodiments, the HARQ process to which thefirst packet flow is assigned is a dedicated HARQ process for a flow forwhich suppression of ACK/NACK is required, said dedicated HARQ processfor the flow not triggering generation of ACK/NACK at the physicallayer.

In various embodiments, the HARQ process ID for the first packet flow iscommunicated in a Radio Resource Control Information Element (RRC IE).In some embodiments, the HARQ process ID is a four bit ID.

In some embodiments, the HARQ process ID to which the first packet flowis assigned identifies a HARQ process to be used for a correspondinguplink transmission block (UL TB) transmitted in an uplink channel.

Assembly of components 1700 further includes a component 1726 configuredto operate the UE to transmit data corresponding to said first packetflow to a second communications device, e.g., a base station, acomponent 1728 configured to identify a second packet flow, said secondpacket flow being a packet flow which does not support and end to endretransmission method, and a component 1730 configured to operate the UEto transmit data to the second communications device without disablingHARQ feedback for the second packet flow.

FIG. 18 is a flowchart 1800 of an exemplary communications method, e.g.,a communications method supporting disabling of HARQ for some trafficflows, in accordance with an exemplary embodiment. Operation starts instep 1801 in which the communications system is powered on andinitialized and proceeds to step 1802.

In step 1802 a first wireless communications device, e.g., a basestation such as a gNB or eNB, including a transmitter, identifies, atthe first wireless communications device, a first traffic flow. Step1802 includes step 1804 in which the first wireless communicationsdevice identifies a first traffic flow that supports an end to endretransmission method in the event of a communications fail of databeing communicated, e.g., the first wireless communications deviceidentifies a TCP traffic flow supporting ACK which satisfies certaincriteria, e.g., QCI/5QI indicating URLLC packets.

Operation proceeds from step 1802 to step 1806. In step 1806 the firstwireless communications device transmits a downlink control information(DCI) scheduling message to a second wireless communications device. Invarious embodiments, the second wireless communications device is anendpoint of said first traffic flow. Step 1806 includes step 1808 inwhich the first wireless communications device transmits an explicitindication in a downlink message to said second wireless communicationsdevice to skip hybrid automatic repeat request (HARQ) feedback for data,corresponding to the first traffic flow, said data being directed to thesecond wireless communications device. In some embodiments, saidexplicit indication to skip Hybrid Automatic Repeat Request (HARQ)feedback for data is a predetermined value in a predetermined field of adownlink control information (DCI) scheduling message. In some suchembodiments said DCI scheduling message is one of a DCI format 1_0 orDCI format 1_1 scheduling message. In some embodiments, saidpredetermined field is a ‘PDSCH-to-HARQ feedback timing indicator’field. In some embodiments, the predetermined value is a value outsidean expected range of values for a PDSCH-to-HARQ feedback timingindicator. In various embodiments said predetermined value is a specificvalue which is indicated via a higher layer parameter. In someembodiments said higher layer parameter is a Slot-timing-value-K1parameter. Operation proceeds from step 1806 to step 1810.

In step 1810 the second wireless communications device receives saiddownlink control information scheduling message. Operation proceeds fromstep 1810 to step 1812. In step 1812 the second wireless communicationsdevice decodes a predetermined field of said downlink controlinformation (DCI) scheduling message. Operation proceeds from step 1812to step 1814.

In step 1814 the second wireless communications device determineswhether or not the predetermined field of the said DCI schedulingmessage communicates a predetermined value, which is the explicitindication to skip hybrid automatic repeat request (HARQ) feedback fordata. Operation proceeds from step 1814 to step 1816.

In step 1816 the first wireless communications device transmits data tothe second wireless communications device with disabled HARQ feedbackfor the first traffic flow. Operation proceeds from step 1816 to step1818.

In step 1818, the second wireless device controls operation as afunction of the determination in step 1814 as to whether or not the DCIscheduling message communicated the predated value in the predeterminedfield which indicated that the second wireless communications deviceshould skip HARQ feedback for data of the first traffic flow. If thedetermination of step 1818 is that the DCI scheduling message doescommunicate the predetermined value in the predetermined field, thenoperation proceeds from step 1818 to step 1820, in which the secondwireless communications device is operated to refrain from includingHARQ-ACK, e.g., HARK ACK or NACK, in uplink control information (UPI)for code block groups (CBGs) and transport blocks (TBs) scheduled in theDCI scheduling message, e.g., corresponding to the first traffic flow.However, if the determination of step 1818 is that the DCI schedulingmessage did not communicate the predetermined value in the predeterminedfield, then operation proceeds from step 1818 to step 1822, in which thesecond wireless communications device is operated to include HARQ-ACK,e.g., HARK ACK or NACK, in uplink control information (UPI) for codeblock groups (CBGs) and transport blocks (TBs) scheduled in the DCIscheduling message, e.g., corresponding to the first traffic flow.Operation proceeds from step 1820 or step 1822 to step 1824.

In step 1824 the first wireless communications device is operated toidentify a second traffic flow, said second traffic flow being a trafficflow which does not support an end to end retransmission method.Operation proceeds from step 1824 to step 1826. In step 1826 the firstwireless communications device is operated to transmit data to thesecond wireless communications device without disabling HARQ feedbackfor the second traffic flow.

FIG. 19 is a drawing of an exemplary assembly of components 1900 whichmay be included in a wireless communications device, e.g., a basestation such as the exemplary base station 700, e.g., a gnB or eNB, ofFIG. 7, and implement steps of an exemplary method, e.g., steps of themethod of the flowchart 1800 of FIG. 18.

Assembly of components 1900 can be, and in some embodiments is, used inbase station 700, e.g., a gNB or eNB, of FIG. 7 or base station 406 orbase station 408 of FIG. 4. The components in the assembly of components1900 can, and in some embodiments are, implemented fully in hardwarewithin the processor 702, e.g., as individual circuits. The componentsin the assembly of components 1900 can, and in some embodiments are,implemented fully in hardware within the assembly of components 708,e.g., as individual circuits corresponding to the different components.In other embodiments some of the components are implemented, e.g., ascircuits, within the processor 702 with other components beingimplemented, e.g., as circuits within assembly of components 708,external to and coupled to the processor 702. As should be appreciatedthe level of integration of components on the processor and/or with somecomponents being external to the processor may be one of design choice.Alternatively, rather than being implemented as circuits, all or some ofthe components may be implemented in software and stored in the memory710 of the base station 700, e.g., a gNB or eNB, with the componentscontrolling operation of the base station to implement the functionscorresponding to the components when the components are executed by aprocessor, e.g., processor 702. In some such embodiments, the assemblyof components 1900 is included in the memory 710 as assembly ofcomponents 722. In still other embodiments, various components inassembly of components 1900 are implemented as a combination of hardwareand software, e.g., with another circuit external to the processorproviding input to the processor 702 which then under software controloperates to perform a portion of a component's function. While processor702 is shown in the FIG. 7 embodiment as a single processor, e.g.,computer, it should be appreciated that the processor 702 may beimplemented as one or more processors, e.g., computers.

When implemented in software the components include code, which whenexecuted by the processor 702, configure the processor 702 to implementthe function corresponding to the component. In embodiments where theassembly of components 1900 is stored in the memory 710, the memory 710is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each component, for causingat least one computer, e.g., processor 702, to implement the functionsto which the components correspond.

Completely hardware based or completely software based components may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented components may be used toimplement the functions. As should be appreciated, the componentsillustrated in FIG. 19 control and/or configure the base station 700, orelements therein such as the processor 702, to perform the functions ofcorresponding steps illustrated and/or described in the method of one ormore of the flowcharts, signaling diagrams and/or described with respectto any of the Figures. Thus the assembly of components 1900 includesvarious components that perform functions of corresponding one or moredescribed and/or illustrated steps of an exemplary method, e.g., stepsof the method of flowchart 1800 of FIG. 18 and/or described or shownwith respect to any of the other figures.

Assembly of components 1900 includes a component 1902 configured toidentify, at a first wireless communications device including atransmitter, a first traffic flow. Component 1902 includes a component1904 configured to identify, at a first wireless communications device,a first traffic flow that supports an end to end retransmission methodin the event of a communications fail of data being communicated.

Assembly of components 1900 further includes a component 1905 configuredto generate at the first wireless communications device a downlinkcontrol information (DCI) scheduling message to be transmitted to asecond wireless communications device, e.g. a UE. Component 1905includes a component 1907 configured to generate at the first wirelesscommunications device an explicit indication in a downlink message tosaid second wireless communications device to skip hybrid automaticrepeat request (HARQ) feedback for data, corresponding to said firsttraffic flow, said data being directed to the second wirelesscommunications device. In various embodiments, the first traffic flow isa downlink traffic flow, e.g., a first downlink traffic flow.

In some embodiments, the explicit indication to skip HARQ feedback fordata is a predetermined value in a predetermined field of a downlinkcontrol information (DCI) scheduling message. In some such embodiments,the DCI scheduling message is one of DCI format 1_0 or DCI format 1_1scheduling message. In some embodiments, the predetermined field is a“PDSCH-to-HARQ_feedback timing indicator’ field. In some embodiments,the predetermined value is a value outside an expected range of valuesfor a PDSCH-to-HARQ feedback timing indicator. In various embodimentssaid predetermined value is a specific value which is indicated via ahigher layer parameter. In some embodiments said higher layer parameteris a Slot-timing-value-K1 parameter.

Assembly of components 1900 further includes a component 1906 configuredto control the first wireless communications device to transmit form thefirst wireless communications device a downlink control informationscheduling message to a second wireless communications device. Component1906 includes a component 1908 configured to control the first wirelesscommunication device to transmit, from the first wireless communicationsdevice, an explicit indication in a downlink message to said secondwireless communications device to skip hybrid automatic repeat request(HARQ) feedback for data, corresponding to said first traffic flow, saiddata being directed to the second wireless communications device.

In some embodiments, said second wireless communications device is anendpoint of said first traffic flow.

Assembly of component 1900 further includes a component 1918 configuredto control the first wireless communications device to transmit data tosecond wireless communications device with disabled HARQ feedback forthe first traffic flow, a component 1924 configured to identify at afirst wireless communications device a second traffic flow, e.g., asecond downlink traffic flow, said second traffic flow being a trafficflow which does not support and end to end retransmission method, and acomponent 1926 configured to transmit, from the first wirelesscommunications device, data to the second wireless communications devicewithout disabling HARQ feedback for the second traffic flow.

FIG. 20 is a drawing of an exemplary assembly of components 2000 whichmay be included in a wireless communications device, e.g., a UE such asthe UE 600 of FIG. 6, and implement steps of an exemplary method, e.g.,steps of the method of the flowchart of FIG. 18.

Assembly of components 2000 can be, and in some embodiments is, used inUE device 600 of FIG. 6 or UE 402 or UE 404 of FIG. 4. The components inthe assembly of components 2000 can, and in some embodiments are,implemented fully in hardware within the processor 602, e.g., asindividual circuits. The components in the assembly of components 2000can, and in some embodiments are, implemented fully in hardware withinthe assembly of components 618, e.g., as individual circuitscorresponding to the different components. In other embodiments some ofthe components are implemented, e.g., as circuits, within the processor602 with other components being implemented, e.g., as circuits withinassembly of components 618, external to and coupled to the processor602. As should be appreciated the level of integration of components onthe processor and/or with some components being external to theprocessor may be one of design choice. Alternatively, rather than beingimplemented as circuits, all or some of the components may beimplemented in software and stored in the memory 620 of the UE 600, withthe components controlling operation of the UE 600 to implement thefunctions corresponding to the components when the components areexecuted by a processor, e.g., processor 602. In some such embodiments,the assembly of components 2000 is included in the memory 620 asassembly of components 654. In still other embodiments, variouscomponents in assembly of components 2000 are implemented as acombination of hardware and software, e.g., with another circuitexternal to the processor providing input to the processor 602 whichthen under software control operates to perform a portion of acomponent's function. While processor 602 is shown in the FIG. 6embodiment as a single processor, e.g., computer, it should beappreciated that the processor 602 may be implemented as one or moreprocessors, e.g., computers.

When implemented in software the components include code, which whenexecuted by the processor 602, configure the processor 602 to implementthe function corresponding to the component. In embodiments where theassembly of components 2000 is stored in the memory 620, the memory 620is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each component, for causingat least one computer, e.g., processor 602, to implement the functionsto which the components correspond.

Completely hardware based or completely software based components may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented components may be used toimplement the functions. As should be appreciated, the componentsillustrated in FIG. 20 control and/or configure the UE 600, or elementstherein such as the processor 602, to perform the functions ofcorresponding steps illustrated and/or described in the method of one ormore of the flowcharts, signaling diagrams and/or described with respectto any of the Figures. Thus the assembly of components 2000 includesvarious components that perform functions of corresponding one or moredescribed and/or illustrated steps of an exemplary method, e.g., stepsof the method of flowchart 1800 of FIG. 18 and/or described or shownwith respect to any of the other figures.

Assembly of components 2000 includes a component 2010 configured tooperate the second wireless communications device to received saiddownlink control information scheduling message, a component 2012configured to decode, at the second wireless communications device, apredetermined field of said downlink control information (DCI)scheduling message, a component 2104 configured to determine, at thesecond wireless communications device, whether or not the predeterminedfield of said downlink control information (DCI) scheduling messagecommunicates a predetermined value, which is the explicit indication toskip hybrid automatic repeat request (HARQ) feedback for data, acomponent 2020 configured to operate the second wireless communicationsdevice to refrain from including the HARQ-ACK, e.g., HARQ ACK or NACK,in the uplink control information (UPI) for code block groups (CBGs) andtransport blocks (TBs) scheduled in the DCI scheduling message, inresponse to a determination that the DCI scheduling message doescommunicate the predetermined value in the predetermined field, and acomponent 2022 configured to operate the second wireless communicationsdevice to include HARQ-ACK, e.g., HARQ ACK or NACK, in the uplinkcontrol information (UPI) for code block groups (CBGs) and transportblocks (TBs) scheduled in the DCI scheduling message, in response to adetermination that the DCI scheduling message does not communicate thepredetermined value in the predetermined field.

FIG. 21 is a flowchart 2100 of an exemplary communications method inaccordance with an exemplary embodiment. Operation starts in 2102 inwhich the communications system implementing the method is powered onand initialized. Operation proceeds from step 2102 to step 2104. In step2104 a first wireless communications device, e.g., a base station suchas a gNB or eNB, including a transmitter, identifies, at the firstwireless communications device, a first traffic flow, e.g., a firstdownlink traffic flow. Step 2104 includes step 2106, in which the firstwireless communications device identifies a first traffic flow, e.g., afirst downlink traffic flow, that supports an end to end retransmissionmethod in the event of a communications failure of data beingcommunicated. Operation proceeds from step 2104 to step 2108.

In step 2108 the first wireless communications device determines if thefirst traffic flow is to be sent using normal mode of communications,e.g., with data encoded via C-RNTI, and with data being uniquelydirected to a second wireless communications device, e.g., a UE. If thedetermination is that first traffic flow is to be sent using normal modeof communications, e.g., with data encoded via C-RNTI, and with databeing uniquely directed to a second wireless communications device, thenoperation proceeds from step 2108 to step 2110; otherwise operationproceeds from step 2108 to step 2114.

In step 2110 the first wireless communications device transmits, fromthe first wireless communications device, an explicit indication to thesecond wireless communications device to skip hybrid automatic repeatrequest (HARQ) feedback for data, corresponding to the first trafficflow, said data being transmitted to the second wireless communicationsdevice. Step 2110 includes step 2112 in which the first wirelesscommunications device transmits, from the first wireless communicationsdevice, a HARQ Off Indicator, set to indicate HARQ is disabled, saidHARQ Off indicator being transmitted in a downlink control information(DCI) format scheduling message, e.g., a DCI Format 1_0 or DCI Format1_1.

In step 2114, the first wireless communications device is operated tocommunicate, e.g., transmit, an explicit indication to the secondwireless communications device to skip HARQ feedback for datacorresponding to the first traffic flow using at least one of aSPS_HARQ_Off_Indicator or a HARQ_Off_Indciator, e.g., using a SPS HARQOff Indicator in a ‘SPS-Config’ RRC IE set to indicate that HARQ isdisabled and including a HARQ Off Indicator, set to indicate HARQ isdisabled, said HARQ Off indicator being transmitted in a downlinkcontrol information (DCI) format scheduling message, e.g., a DCI Format1_0 or DCI Format 1_1.

Operation proceeds from step 2110 or step 2114 to step 2116. In step2116 the first wireless communications device is operated to transmitfirst traffic flow data to the second wireless communications device.Operation proceeds from step 2116 to step 2118.

In step 2118 the first second wireless communications device is operatedto ignore at least one of: i) information in a physical downlink sharedchannel (PDSCH)-to-HARQ_feedback_timing field or ii) information in aHARQ process number field of downlink control information provided bythe first wireless communications device with respect to the firsttraffic flow. Operation proceeds from step 2118 to step 2120.

In step 2120 the first wireless communications device identifies, at thefirst wireless communications device, a second traffic flow, said secondtraffic flow being a traffic flow which does not support an end to endretransmission method. Operation proceeds from step 2120 to step 2122.

In step 2122 the first wireless communications device transmits data tothe second wireless communications device without disabling HARQfeedback for the second traffic flow.

FIG. 22 is a drawing of an exemplary assembly of components 2200 whichmay be included in a wireless communications device, e.g., a basestation such as the exemplary base station 700, e.g., a gNB or eNB, ofFIG. 7, and implement steps of an exemplary method, e.g., steps of themethod of the flowchart 2100 of FIG. 21.

Assembly of components 2200 can be, and in some embodiments is, used inbase station 700, e.g., a gNB or eNB, of FIG. 7 or base station 406 orbase station 408 of FIG. 4. The components in the assembly of components2200 can, and in some embodiments are, implemented fully in hardwarewithin the processor 702, e.g., as individual circuits. The componentsin the assembly of components 2200 can, and in some embodiments are,implemented fully in hardware within the assembly of components 708,e.g., as individual circuits corresponding to the different components.In other embodiments some of the components are implemented, e.g., ascircuits, within the processor 702 with other components beingimplemented, e.g., as circuits within assembly of components 708,external to and coupled to the processor 702. As should be appreciatedthe level of integration of components on the processor and/or with somecomponents being external to the processor may be one of design choice.Alternatively, rather than being implemented as circuits, all or some ofthe components may be implemented in software and stored in the memory710 of the base station 700, e.g., a gNB or eNB, with the componentscontrolling operation of the base station to implement the functionscorresponding to the components when the components are executed by aprocessor, e.g., processor 702. In some such embodiments, the assemblyof components 2200 is included in the memory 710 as assembly ofcomponents 722. In still other embodiments, various components inassembly of components 2200 are implemented as a combination of hardwareand software, e.g., with another circuit external to the processorproviding input to the processor 702 which then under software controloperates to perform a portion of a component's function. While processor702 is shown in the FIG. 7 embodiment as a single processor, e.g.,computer, it should be appreciated that the processor 702 may beimplemented as one or more processors, e.g., computers.

When implemented in software the components include code, which whenexecuted by the processor 702, configure the processor 702 to implementthe function corresponding to the component. In embodiments where theassembly of components 2200 is stored in the memory 710, the memory 710is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each component, for causingat least one computer, e.g., processor 702, to implement the functionsto which the components correspond.

Completely hardware based or completely software based components may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented components may be used toimplement the functions. As should be appreciated, the componentsillustrated in FIG. 22 control and/or configure the base station 700, orelements therein such as the processor 702, to perform the functions ofcorresponding steps illustrated and/or described in the method of one ormore of the flowcharts, signaling diagrams and/or described with respectto any of the Figures. Thus the assembly of components 2200 includesvarious components that perform functions of corresponding one or moredescribed and/or illustrated steps of an exemplary method, e.g., stepsof the method of flowchart 2100 of FIG. 21 and/or described or shownwith respect to any of the other figures.

Assembly of components 2200 includes a component 2204 configured toidentify, at a first wireless communications device, e.g., a basestation, including a transmitter, a first traffic flow, e.g., a firstdownlink traffic flow. Component 2204 includes a component 2206configured to identify a first traffic flow that supports an end to endretransmission method in the event of a communications failure of databeing communicated. Assembly of components 2200 further includes acomponent 2208 configured to determine if the first traffic flow data isto be sent using normal mode of communications, e .g., with data encodedvia C-RNTI, and with data being uniquely directed to a second wirelesscommunications device, e.g., a UE, and to control operation as afunction of the determination.

Assembly of components 2200 further includes a component 2210 configuredto operate the first wireless communications device to transmit, fromthe first wireless communications device, an explicit indication to asecond wireless communications device to skip hybrid automatic repeatrequest (HARQ) feedback for data, corresponding to the first trafficflow, said data being transmitted to the second wireless communicationsdevice, e.g., in response to a determination that the first traffic flowis to be sent using the normal mode of communications. Component 2210includes a component 2212 configured to operate the first wirelesscommunications device to transmit, from the first wirelesscommunications to the second wireless communications device, a HARQ OffIndicator set to indicate HARQ is disabled, said HARQ Off Indicatorbeing transmitted in a downlink control information format schedulingmessage, e.g., a DCI Format 1_0 or Format 1_1. In some embodiments, theHARQ Off Indicator is a one bit value set to a predetermined value, e.g.1, when HARQ is disabled.

Assembly of components 2200 further includes a component 2214 configuredto operate the first communications device to communicate an explicitindication to the second wireless communications device to sjip HARQfeedback for data corresponding to the first traffic flow using at leastone of a SPS HARQ Off Indicator or a HARQ Off Indicator, e.g., e.g., inresponse to a determination that the first traffic flow is to be sentusing an semi-persistent scheduling SPS mode of communications.Component 2214 includes a component 22141 configured to operate thefirst wireless communications device to transmit, from the firstwireless communications device to the second wireless communicationsdevice, a SPS HARQ Off Indicator, set to indicate HARQ is disabled in aSPS_CONFIG RRC IE, and a component 22142 configured to operate the firstwireless communications device to transmit from the first wirelesscommunications device to the second wireless communications device, aHARQ Off Indicator set to indicate HARQ is disabled, said HARQ OffIndicator being transmitted in a downlink control information formatscheduling message, e.g., a DCI Format 1_0 or Format 1_1. In someembodiments, the SPS HARQ Off Indicator is a one bit value set to apredetermined value, e.g. 1, when HARQ is disabled. In some embodiments,the HARQ Off Indicator is a one bit value set to a predetermined value,e.g. 1, when HARQ is disabled.

Assembly of component 2200 further includes a component 2216 configuredto operate the first wireless communications device to transmit firsttraffic flow data to the second wireless communications device, acomponent 2220 configured to identify, at the first wirelesscommunications device, a second traffic flow, said second traffic flowbeing a traffic flow which does not support and end to endretransmission method, an a component 2222 configured to transmit datato the second wireless communications device without disabling HARQfeedback for the second traffic flow.

FIG. 23 is a flowchart 2300 of an exemplary method of operating a firstwireless communications device including a transmitter in accordancewith an exemplary embodiment, e.g., an exemplary method of operating thefirst wireless communications device to signal suppression and suppressRLC ACK/NACK corresponding to selected acknowledged mode protocol dataunits (AM PDUs), in accordance with an exemplary embodiment. The firstwireless communications device is, e.g., a base station such as gNB oreNB, or a user equipment (UE) device. Operation starts in step 2302 inwhich the first wireless communications device is powered on andinitialized. Operation proceeds from start step 2302 to step 2304.

In step 2304, the first wireless communications device identifies apacket data convergence protocol (PDCP) packet corresponding to radiolink control acknowledged mode (RLC AM). Operation proceeds from step2304 to step 2306.

In step 2306 the first wireless communications device generates anacknowledged mode protocol data unit (AM PDU) including a No RLC ACKRequired (NRAR) indicator from the identified PDCP packet. In variousembodiments, the AM PDU is an acknowledged mode data protocol data unit(AMD PDU). In some embodiments, the NRAR indicator is a one bitindicator. In some embodiments, the NRAR indicator is the first bit inan octet. In some embodiments, the NRAR indicator is set to one toindicate an RLC ACK is not required. In some such embodiments, the NRARindicator is set to zero to indicate that an RLC ACK is expected.

Step 2306 includes steps 2308, 2310, 2311 and 2312. In step 2308, thefirst wireless communications device determines if a segment offset (SO)is to be included in the AM PDU. If a segment offset is not to beincluded in the AM PDU which is being generated, then operation proceedsfrom step 2308 to step 2310; otherwise, operation proceeds from step2308 to step 2311.

In step 2310, the first wireless communications device inserts the NoRLC ACK Required (NRAR) indicator after a sequence number (SN) in anacknowledged mode (AM) PDU, which is being generated, said AM PDU whichis being generated not including a segment offset (SO). Step 2310includes steps 2314 and 2316. One of step 2314 and 2316 is performed foran iteration of step 2310, e.g., based on whether or not the firstwireless communications device wants to suppress RLC ACK for the AM PDUbeing generated, e.g., based on whether or not the generated AM PDUcorresponds to a PDCP packet of a flow for which RLC ACK is to besuppressed, e.g., a TCP traffic flow supporting end to endretransmission in the event of a communications failure.

In step 2314 the first wireless communications device sets the NRAR toone to indicate that ACK is not required. In step 2316 the firstwireless communications device sets the NRAR to zero to indicate thatACK is expected.

In step 2311 the first wireless communications device includes a segmentoffset (SO) in the AM PDU which is being generated. Operation proceedsfrom step 2311 to step 2312.

In step 2312, the first wireless communications device inserts the NoRLC ACK Required (NRAR) indicator after a sequence office (SO) in anacknowledged mode (AM) PDU, which is being generated, said AM PDU whichis being generated including a segment offset (SO). Step 2312 includessteps 2318 and 2320. One of step 2318 and 2320 is performed for aniteration of step 2312, e.g., based on whether or not the first wirelesscommunications device wants to suppress RLC ACK for the AM PDU beinggenerated, e.g., based on whether or not the generated AM PDUcorresponds to a PDCP packet of a flow for which RLC ACK is to besuppressed, e.g., a TCP traffic flow supporting end to endretransmission in the event of a communications failure.

In step 2318 the first wireless communications device sets the NRAR toone to indicate that ACK is not required. In step 2320 the firstwireless communications device sets the NRAR to zero to indicate thatACK is expected.

In some embodiments, step 2306 may, be and sometimes is performedmultiple times, e.g., with a set of AM PDUs being generatedcorresponding to the identified PDCP packet.

Operation proceeds from step 2306 to step 2322. In step 2322 the radiotransmitter in the wireless communications device is operated totransmit the AMD PDU to a second wireless communications, e.g., a UE orbase station. For example, if the first communications device is a basestation, the second communications device is, in some embodiments, auser equipment device. As another example, if the first communicationsdevice is a UE device, the second communications device is, in someembodiments, a base station.

In some embodiments, operation proceeds from step 2322 to step 2324. Insome other embodiments, operation proceeds from step 2322 to step 2326.

In step 2324 the first wireless communications device in transmits asecond AM PDU, e.g., a second AMD PDU, to the second wirelesscommunications device, said second AM PDU including a NRAR indicator setto 1 indicating an RLC ACK is not required.

In step 2326 the first wireless communications device receives an RLCstatus PDU from the second wireless communications device, said RLCstatus PDU including an ACK report from the second wirelesscommunications device.

In one exemplary embodiment, the transmitted AMD PDU, e .g., of step2322, included a NRAR indicator set to 0, and the received RLC statusPDU includes: i) a sequence number for the transmitted PDU and ii) andan ACK/NACK indication corresponding to the transmitted AM PDU.

In another exemplary embodiment, the transmitted PDU of step 2322included a NRAR indicator set to 0; step 2324 is performed, and thetransmitted second AM PDU of step 2324 included a NRAR indicator set to1 indicating an RLC ACK is not required, and the received RLC status PDUof step 2326 includes: i) a sequence number for the AM PDU, and ii) aACK/NACK indication corresponding to the AM PDU with NRAR indicator setto 0, and said RLC status PDU does not include a sequence number or anACK/NACK indication corresponding to the transmitted second AM PDU,which included the status bit set to one, said second wirelesscommunications device having intentionally left out the sequence numbercorresponding to the second AM PDU.

In another exemplary embodiment, both the transmitted AM PDU of step2322 and the second AM PDU of step 2324 have their NRAR indicator set to1, and step 2326 is not performed. In some embodiments, the firstwireless communications device stores information as to which AM PDUshave been transmitted with the NRAR indicator set to 1, and the firstwireless communications device is controlled to refrain from monitoringto receive for ACK/NACK reports corresponding to those AM PDUs.

FIG. 24 is a drawing of an exemplary assembly of components 2400 whichmay be included in a first wireless communications device, e.g., a basestation such as the exemplary base station 700, e.g., a gNB or eNB, ofFIG. 7 or a UE such as the exemplary UE 600 of FIG. 6, and implementsteps of an exemplary method, e.g., steps of the method of the flowchart2300 of FIG. 23.

Assembly of components 2400 can be, and in some embodiments is, used inbase station 700, e.g., a gNB or eNB, of FIG. 7 or base station 406 orbase station 408 of FIG. 4. The components in the assembly of components2400 can, and in some embodiments are, implemented fully in hardwarewithin the processor 702, e.g., as individual circuits. The componentsin the assembly of components 2400 can, and in some embodiments are,implemented fully in hardware within the assembly of components 708,e.g., as individual circuits corresponding to the different components.In other embodiments some of the components are implemented, e.g., ascircuits, within the processor 702 with other components beingimplemented, e.g., as circuits within assembly of components 708,external to and coupled to the processor 702. As should be appreciatedthe level of integration of components on the processor and/or with somecomponents being external to the processor may be one of design choice.Alternatively, rather than being implemented as circuits, all or some ofthe components may be implemented in software and stored in the memory710 of the base station 700, e.g., a gNB or eNB, with the componentscontrolling operation of the base station to implement the functionscorresponding to the components when the components are executed by aprocessor, e.g., processor 702. In some such embodiments, the assemblyof components 2400 is included in the memory 710 as assembly ofcomponents 722. In still other embodiments, various components inassembly of components 2400 are implemented as a combination of hardwareand software, e.g., with another circuit external to the processorproviding input to the processor 702 which then under software controloperates to perform a portion of a component's function. While processor702 is shown in the FIG. 7 embodiment as a single processor, e.g.,computer, it should be appreciated that the processor 702 may beimplemented as one or more processors, e.g., computers.

When implemented in software the components include code, which whenexecuted by the processor 702, configure the processor 702 to implementthe function corresponding to the component. In embodiments where theassembly of components 2400 is stored in the memory 710, the memory 710is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each component, for causingat least one computer, e.g., processor 702, to implement the functionsto which the components correspond.

Completely hardware based or completely software based components may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented components may be used toimplement the functions. As should be appreciated, the componentsillustrated in FIG. 24 control and/or configure the base station 700, orelements therein such as the processor 702, to perform the functions ofcorresponding steps illustrated and/or described in the method of one ormore of the flowcharts, signaling diagrams and/or described with respectto any of the Figures. Thus the assembly of components 2400 includesvarious components that perform functions of corresponding one or moredescribed and/or illustrated steps of an exemplary method, e.g., stepsof the method of flowchart 2300 of FIG. 23 and/or described or shownwith respect to any of the other figures.

Assembly of components 2400 can be, and in some embodiments is, used inUE device 600 of FIG. 6 or UE 402 or UE 404 of FIG. 4. The components inthe assembly of components 2400 can, and in some embodiments are,implemented fully in hardware within the processor 602, e.g., asindividual circuits. The components in the assembly of components 2400can, and in some embodiments are, implemented fully in hardware withinthe assembly of components 618, e.g., as individual circuitscorresponding to the different components. In other embodiments some ofthe components are implemented, e.g., as circuits, within the processor602 with other components being implemented, e.g., as circuits withinassembly of components 618, external to and coupled to the processor602. As should be appreciated the level of integration of components onthe processor and/or with some components being external to theprocessor may be one of design choice. Alternatively, rather than beingimplemented as circuits, all or some of the components may beimplemented in software and stored in the memory 620 of the UE 600, withthe components controlling operation of the UE 600 to implement thefunctions corresponding to the components when the components areexecuted by a processor, e.g., processor 602. In some such embodiments,the assembly of components 2400 is included in the memory 620 asassembly of components 654. In still other embodiments, variouscomponents in assembly of components 2400 are implemented as acombination of hardware and software, e.g., with another circuitexternal to the processor providing input to the processor 602 whichthen under software control operates to perform a portion of acomponent's function. While processor 602 is shown in the FIG. 6embodiment as a single processor, e.g., computer, it should beappreciated that the processor 602 may be implemented as one or moreprocessors, e.g., computers.

When implemented in software the components include code, which whenexecuted by the processor 602, configure the processor 602 to implementthe function corresponding to the component. In embodiments where theassembly of components 2400 is stored in the memory 620, the memory 620is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each component, for causingat least one computer, e.g., processor 602, to implement the functionsto which the components correspond.

Completely hardware based or completely software based components may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented components may be used toimplement the functions. As should be appreciated, the componentsillustrated in FIG. 24 control and/or configure the UE 600, or elementstherein such as the processor 602, to perform the functions ofcorresponding steps illustrated and/or described in the method of one ormore of the flowcharts, signaling diagrams and/or described with respectto any of the Figures. Thus the assembly of components 2400 includesvarious components that perform functions of corresponding one or moredescribed and/or illustrated steps of an exemplary method, e.g., stepsof the method of flowchart 2300 of FIG. 23 and/or described or shownwith respect to any of the other figures.

Assembly of components 2400 includes a component 2404 configured toidentify a packet data convergence protocol (PDCP) packet correspondingto radio link control acknowledged mode (RLC AM), a component 2406configured to generate an acknowledged mode protocol data unit (AM PDU),e.g., an AMD PDU, including a No RLC ACK Required (NRAR) indicator, acomponent 2422 configured to operate the radio transmitter in the firstwireless communications device to transmit the AM PDU to a secondwireless communications device, a component 2424 configured to transmita second AM PDU, e.g., a second AMD PDU, including a No RLC ACK Requiredindicator set to 1 indicating RLC ACK is not required, and a component2426 configured to operate the first wireless communications device toreceive a RLC status PDU from the second wireless communications deviceand recover information communicated in the RLC status PDU.

In some embodiments, the NRAR indicator is a one bit indicator. In someembodiments, the NRAR indicator is the first bit in an octet. In someembodiments, the NRAR indicator is set to one to indicate an RLC ACK isnot required. In some such embodiments, the NRAR indicator is set tozero to indicate that an RLC ACK is expected.

Component 2406 includes a component 2408 configured to determine if asegment offset (SO) is to be included in the AM PDU and to controloperation as a function of the determination, a component 2409configured to include a segment offset (SO) in the AM PDU which is beinggenerated, a component 2410 configured to insert the No RLC ACK Required(NRAR) after a sequence number in an acknowledged mode PDU with nosegment offset, and a component 2412 configured to insert the No RLC ACKRequired (NRAR) indicator after a segment offset (SO) in an acknowledgedmode PDU with a SO.

Component 2410 includes a component 2414 configured to set the NRAR toone to indicate that ACK/NACK is not required, e.g., in response to adetermination by the first wireless communications device that ACKfeedback is not required in response to this generated AM PDU which isto be transmitted. Component 2410 further includes a component 2416configured to set the NRAR to zero to indicate that ACK/NCK is expected,e.g., in response to a determination by the first wirelesscommunications device that ACK feedback is expected in response to thisgenerated AM PDU which is to be transmitted.

Component 2412 includes a component 2418 configured to set the NRAR toone to indicate that ACK/NACK is not required, e.g., in response to adetermination by the first wireless communications device that ACKfeedback is not required in response to this generated AM PDU which isto be transmitted. Component 2412 further includes a component 2420configured to set the NRAR to zero to indicate that ACK/NACK isexpected, e.g., in response to a determination by the first wirelesscommunications device that ACK feedback is expected in response to thisgenerated AM PDU which is to be transmitted.

In some embodiments, the RLC STATUS PDU received by component 2426 may,and sometimes does, include: i) a sequence number and ii) an ACK/NACKindication corresponding to the transmitted AM PDU which included a NRARset to zero, but does not include: i) a sequence number and ii) anACK/NACK indication corresponding to the second transmitted AM PDU whichincluded the NRAR indicator set to one, said second wirelesscommunications device having intentionally omitted the sequence numbercorresponding to second transmitted AM PDU and an ACK/NACK indicationcorresponding to second transmitted AM PDU.

Assembly of components 2400 includes a component 2428 configured tooperate the first wireless communications device to selectively monitorfor ACKs/NACKs based on the value of the NRAR indicator in eachtransmitted AM PDU, which included an NRAR indicator. In one embodiment,if the value of the NRAR indicator in the transmitted AM PDU was one,then component 2428 controls the first wireless communications device torefrain from monitoring for an ACK/NACK corresponding to thattransmitted AM PDU, and if the value of the NRAR indicator in thetransmitted AM PDU was zero, then component 2428 control the firstwireless communications device to monitor for an ACK/NACK correspondingto that transmitted AM PDU.

FIG. 25 is a drawing 2500 illustrating exemplary wireless communicationsdevices (first wireless communications device 2502, second wirelesscommunications device 2504) in which one or more HARQ processes may be,and sometimes are, designated and used, e.g., temporarily designated andused as HARQ suppression processes. In one embodiment, first wirelesscommunications device 2502 is a base station, e.g., a gNB or eNB, andsecond wireless communications device 2504 is a user equipment (UE)device. In another embodiment, first wireless communications device 2502is a user equipment (UE) device, and second wireless communicationsdevice 2504 is a base station, e.g., a gNB or eNB. The device shown inFIG. 25 which is a UE is, e.g. UE 600 of FIG. 6, and the device shown inFIG. 25 which is a base station is, e.g., base station 700 of FIG. 7.

First wireless communications device 2502 includes a HARQ transmittercomponent 2506. HARQ transmitter component 2506 includes 16 HARQprocesses (HARQ process #1 2510 with corresponding HARQ process ID=0,HARQ process #2 2512 with corresponding HARQ process ID=1, HARQ process#3 2514 with corresponding HARQ process ID=2, HARQ process #4 2516 withcorresponding HARQ process ID=3, HARQ process #5 2518 with correspondingHARQ process ID=4, HARQ process #6 2520 with corresponding HARQ processID=5, HARQ process #7 2522 with corresponding HARQ process ID=6, HARQprocess #8 2524 with corresponding HARQ process ID=7, HARQ process #92526 with corresponding HARQ process ID=8, HARQ process #10 2528 withcorresponding HARQ process ID=9, HARQ process #11 2530 withcorresponding HARQ process ID=10, HARQ process #12 2532 withcorresponding HARQ process ID=11, HARQ process #13 2534 withcorresponding HARQ process ID=12, HARQ process #14 2536 withcorresponding HARQ process ID=13, HARQ process #15 2538 withcorresponding HARQ process ID=14, HARQ process #16 2540 withcorresponding HARQ process ID=15).

Second wireless communications device 2505 includes a HARQ receivercomponent 2508. HARQ receiver component 2508 includes 16 HARQ processes(HARQ process #1 2550 with corresponding HARQ process ID=0, HARQ process#2 2552 with corresponding HARQ process ID=1, HARQ process #3 2554 withcorresponding HARQ process ID=2, HARQ process #4 2556 with correspondingHARQ process ID=3, HARQ process #5 2558 with corresponding HARQ processID=4, HARQ process #6 2560 with corresponding HARQ process ID=5, HARQprocess #7 2562 with corresponding HARQ process ID=6, HARQ process #82564 with corresponding HARQ process ID=7, HARQ process #9 2566 withcorresponding HARQ process ID=8, HARQ process #10 2568 withcorresponding HARQ process ID=9, HARQ process #11 2570 withcorresponding HARQ process ID=10, HARQ process #12 2572 withcorresponding HARQ process ID=11, HARQ process #13 2574 withcorresponding HARQ process ID=12, HARQ process #14 2576 withcorresponding HARQ process ID=13, HARQ process #15 2578 withcorresponding HARQ process ID=14, HARQ process #16 2580 withcorresponding HARQ process ID=15).

In various embodiments, K of the 16 HARQ processes may be, andsometimes, are designated, e .g., temporarily designated, as HARQprocesses for which ACK/NACK feedback for data is to be suppressed,e.g., HARQ suppression processes. In some embodiments, a designated HARQsuppression process does not expect ACK/NACK feedback in response totransmitted data, does not generate ACK/NACK feedback in response totransmitted data, and/or proceeds under the assumption that there willnot be ACK/NACK feedback in response to transmitted data.

FIG. 26 is a drawing 2600 illustrating an example of the first andsecond communications devices (2502, 2504) of FIG. 25, in which K=4, and4 of the 16 HARQ processes have been designated as HARQ suppressionprocesses, and further illustrating assignment of a first type of packetflow to a designated HARQ suppression process, and assignment of asecond type of packet flow to a HARQ process which does not suppressfeedback of ACK/NACK for data. Drawing 2600 of FIG. 26 further includeslegend 2605. Legend 2605 identifies that the * symbol 2607 is used toindicate a HARQ process ID and corresponding HARQ process which isdesignated and used, e.g., temporarily designated and used, as a HARQsuppression process, e.g. in which ACK/NACK feedback for data isskipped.

Legend 2605 further indicates that symbol 2609, which is a box including(PF1), is used to indicated which HARQ process packet flow 1, e.g., aTCP packet flow supporting end to end retransmission of packets, hasbeen assigned to. Legend 2605 further indicates that symbol 2611, whichis a box including (PF2), is used to indicate which HARQ process packetflow 2, e.g., a packet flow not supporting end to end retransmission ofpackets, has been assigned to.

Drawings 2601 and 2603 of FIG. 26 illustrates, by use of the * symbol2607, that the 4 selected HARQ processes which are designated as HARQsuppression processes are HARQ process #13 with HARQ process ID=12, HARQprocess #14 with HARQ process ID=13, HARQ process #15 with HARQ processID=14, and HARQ process #14 with HARQ process ID=15.

Drawing 2601 further illustrates that packet flow 1, e.g., a TCP packetflow supporting end to end retransmission of packets, has been assignedto HARQ process #13 with HARQ process ID=12, which has been designatedas a HARQ suppression process, which does not provide ACK/NACK feedbackin response to transmitted data.

Drawing 2601 further illustrates that packet flow 2, e.g., a packet flowthat does not support end to end retransmission of packets, has beenassigned to HARQ process #1 with HARQ process ID=0, which is a normalHARQ process which supports ACK/NACK feedback in response to transmitteddata.

FIG. 27 is a drawing 2700 illustrating exemplary wireless communicationsdevices (first wireless communications device 2702, second wirelesscommunications device 2704) in which some HARQ processes are dedicatedHARQ processes with a corresponding ID for a flow for which suppressionof ACK/NACK is required and ACK/NACK feedback in response to data is notcommunicated or used, while other HARQ processes are normal HARQprocesses in which ACK/NACK feedback in response to data is supported.In one embodiment, first wireless communications device 2702 is a basestation, e.g., a gNB or eNB, and second wireless communications device2704 is a user equipment (UE) device. In another embodiment, firstwireless communications device 2702 is a user equipment (UE) device, andsecond wireless communications device 2704 is a base station, e.g., agNB or eNB. The device shown in FIG. 27 which is a UE is, e.g. UE 600 ofFIG. 6, and the device shown in FIG. 27 which is a base station is,e.g., base station 700 of FIG. 7.

First wireless communications device 2702 includes a HARQ transmittercomponent 2706. HARQ transmitter component 2706 includes 20 HARQprocesses (HARQ process #1 2710 with corresponding HARQ process ID=0,HARQ process #2 2712 with corresponding HARQ process ID=1, HARQ process#3 2714 with corresponding HARQ process ID=2, HARQ process #4 2716 withcorresponding HARQ process ID=3, HARQ process #5 2718 with correspondingHARQ process ID=4, HARQ process #6 2720 with corresponding HARQ processID=5, HARQ process #7 2722 with corresponding HARQ process ID=6, HARQprocess #8 2724 with corresponding HARQ process ID=7, HARQ process #92726 with corresponding HARQ process ID=8, HARQ process #10 2728 withcorresponding HARQ process ID=9, HARQ process #11 2730 withcorresponding HARQ process ID=10, HARQ process #12 2732 withcorresponding HARQ process ID=11, HARQ process #13 2734 withcorresponding HARQ process ID=12, HARQ process #14 2736 withcorresponding HARQ process ID=13, HARQ process #15 2738 withcorresponding HARQ process ID=14, HARQ process #16 2740 withcorresponding HARQ process ID=15, HARQ process #2 2742 withcorresponding HARQ process ID=16, HARQ process #3 2744 withcorresponding HARQ process ID=17, HARQ process #4 2746 withcorresponding HARQ process ID=18, HARQ process #5 2748 withcorresponding HARQ process ID=19).

Second wireless communications device 2705 includes a HARQ receivercomponent 2708. HARQ receiver component 2708 includes 16 HARQ processes(HARQ process #1 2750 with corresponding HARQ process ID=0, HARQ process#2 2752 with corresponding HARQ process ID=1, HARQ process #3 2754 withcorresponding HARQ process ID=2, HARQ process #4 2756 with correspondingHARQ process ID=3, HARQ process #5 2758 with corresponding HARQ processID=4, HARQ process #6 2760 with corresponding HARQ process ID=5, HARQprocess #7 2762 with corresponding HARQ process ID=6, HARQ process #82764 with corresponding HARQ process ID=7, HARQ process #9 2766 withcorresponding HARQ process ID=8, HARQ process #10 2768 withcorresponding HARQ process ID=9, HARQ process #11 2770 withcorresponding HARQ process ID=10, HARQ process #12 2772 withcorresponding HARQ process ID=11, HARQ process #13 2774 withcorresponding HARQ process ID=12, HARQ process #14 2776 withcorresponding HARQ process ID=13, HARQ process #15 2778 withcorresponding HARQ process ID=14, HARQ process #16 2780 withcorresponding HARQ process ID=15, HARQ process #2 2782 withcorresponding HARQ process ID=16, HARQ process #3 2784 withcorresponding HARQ process ID=17, HARQ process #4 2786 withcorresponding HARQ process ID=18, HARQ process #5 2788 withcorresponding HARQ process ID=19).

Drawing 2700 of FIG. 27 further includes legend 2705. Legend 2705identifies that the * symbol 2707 is used to indicate a dedicated HARQprocess and corresponding HARQ process ID, which is intended to be usedfor a flow for which suppression of ACK/NACK is required or desired. Insome embodiments, such HARQ processes are designated as HARQ suppressionprocesses. In the example of FIG. 27, the first 16 HARQ processes andcorresponding IDs, support ACK/NACK in response to transmitted data,while the last 4 16 HARQ processes and corresponding IDs, are dedicatedHARQ suppression processes which do not support ACK/NACK in response totransmitted data.

FIG. 28 is a drawing 2800 illustrating an example of the first andsecond communications devices (2702, 2704) of FIG. 27, in which 4 of the20 HARQ processes are dedicated HARQ suppression processes, and furtherillustrating assignment of a first type of packet flow to a dedicatedHARQ suppression process, and assignment of a second type of packet flowto a HARQ process which does not suppress feedback of ACK/NACK for data.Drawing 2800 of FIG. 28 further includes legend 2801. Legend 2801identifies that the * symbol 2707 is used to indicate a HARQ process IDand corresponding HARQ process which is dedicate a HARQ suppressionprocess, e.g. in which ACK/NACK feedback for data is not communicated,expected, or used.

Legend 2810 further indicates that symbol 2809, which is a box including(PF1), is used to indicated which HARQ process packet flow 1, e.g., aTCP packet flow supporting end to end retransmission of packets, hasbeen assigned to. Legend 2801 further indicates that symbol 2811, whichis a box including (PF2), is used to indicate which HARQ process packetflow 2, e.g., a packet flow not supporting end to end retransmission ofpackets, has been assigned to.

Drawings 2800 illustrates, by use of the * symbol 2807, that HARQprocesses which are dedicated HARQ suppression processes are HARQprocess #17 with HARQ process ID=16, HARQ process #18 with HARQ processID=17, HARQ process #19 with HARQ process ID=18, and HARQ process #20with HARQ process ID=19.

Drawing 2800 further illustrates that packet flow 1, e.g., a TCP packetflow supporting end to end retransmission of packets, has been assignedto HARQ process #17 with HARQ process ID=16, which is a dedicated HARQsuppression process, which does not provide ACK/NACK feedback inresponse to transmitted data.

Drawing 2800 further illustrates that packet flow 2, e.g., a packet flowthat does not support end to end retransmission of packets, has beenassigned to HARQ process #1 with HARQ process ID=0, which is a normalHARQ process which supports ACK/NACK feedback in response to transmitteddata.

FIG. 29 is a drawing 2900 illustrating exemplary wireless communicationsdevices (first wireless communications device 2902, second wirelesscommunications device 2904) in which some HARQ processes are dedicatedHARQ processes with a corresponding ID for a flow for which suppressionof ACK/NACK is required and ACK/NACK feedback in response to data is notcommunicated or used, while other HARQ processes are normal HARQprocesses in which ACK/NACK feedback in response to data is supported.In one embodiment, first wireless communications device 2902 is a basestation, e.g., a gNB or eNB, and second wireless communications device2904 is a user equipment (UE) device. In another embodiment, firstwireless communications device 2902 is a user equipment (UE) device, andsecond wireless communications device 2904 is a base station, e.g., agNB or eNB. The device shown in FIG. 29 which is a UE is, e.g. UE 600 ofFIG. 6, and the device shown in FIG. 29 which is a base station is,e.g., base station 700 of FIG. 7.

First wireless communications device 2902 includes a HARQ transmittercomponent 2906. HARQ transmitter component 2906 includes 20 HARQprocesses (HARQ process #1 2910 with corresponding HARQ process ID=0,HARQ process #2 2912 with corresponding HARQ process ID=1, HARQ process#3 2914 with corresponding HARQ process ID=2, HARQ process #4 2916 withcorresponding HARQ process ID=3, HARQ process #5 2918 with correspondingHARQ process ID=4, HARQ process #6 2920 with corresponding HARQ processID=5, HARQ process #7 2922 with corresponding HARQ process ID=6, HARQprocess #8 2924 with corresponding HARQ process ID=7, HARQ process #92926 with corresponding HARQ process ID=8, HARQ process #10 2928 withcorresponding HARQ process ID=9, HARQ process #11 2930 withcorresponding HARQ process ID=10, HARQ process #12 2932 withcorresponding HARQ process ID=11, HARQ process #13 2934 withcorresponding HARQ process ID=12, HARQ process #14 2936 withcorresponding HARQ process ID=13, HARQ process #15 2938 withcorresponding HARQ process ID=14, HARQ process #16 2940 withcorresponding HARQ process ID=15, HARQ process #17 2942 withcorresponding HARQS process ID=0, HARQ process #18 2944 withcorresponding HARQS process ID=1, HARQ process #19 2946 withcorresponding HARQS process ID=2, HARQ process #20 2948 withcorresponding HARQS process ID=3).

In the exemplary embodiment of FIG. 29, different variables and/ordifferent fields are used to communicated the ID corresponding to theHARQ process depending upon the type of HARQ process, e.g., there is aHARQ process ID variable used for HARQ processes which support ACK/NACK,and there is a HARQS process ID variable used for dedicated HARQprocesses which suppress ACK/NACK.

Second wireless communications device 2905 includes a HARQ receivercomponent 2908. HARQ receiver component 2908 includes 16 HARQ processes(HARQ process #1 2950 with corresponding HARQ process ID=0, HARQ process#2 2952 with corresponding HARQ process ID=1, HARQ process #3 2954 withcorresponding HARQ process ID=2, HARQ process #4 2956 with correspondingHARQ process ID=3, HARQ process #5 2958 with corresponding HARQ processID=4, HARQ process #6 2960 with corresponding HARQ process ID=5, HARQprocess #7 2962 with corresponding HARQ process ID=6, HARQ process #82964 with corresponding HARQ process ID=7, HARQ process #9 2966 withcorresponding HARQ process ID=8, HARQ process #10 2968 withcorresponding HARQ process ID=9, HARQ process #11 2970 withcorresponding HARQ process ID=10, HARQ process #12 2972 withcorresponding HARQ process ID=11, HARQ process #13 2974 withcorresponding HARQ process ID=12, HARQ process #14 2976 withcorresponding HARQ process ID=13, HARQ process #15 2978 withcorresponding HARQ process ID=14, HARQ process #16 2980 withcorresponding HARQ process ID=15, HARQ process #17 2982 withcorresponding HARQS process ID=0, HARQ process #18 2984 withcorresponding HARQS process ID=1, HARQ process #19 2986 withcorresponding HARQS process ID=2, HARQ process #20 2988 withcorresponding HARQS process ID=3).

Drawing 2900 of FIG. 29 further includes legend 2905. Legend 2905identifies that the * symbol 2907 is used to indicate a dedicated HARQprocess and corresponding HARQ process ID, which is intended to be usedfor a flow for which suppression of ACK/NACK is required or desired. Insome embodiments, such HARQ processes are designated as HARQ suppressionprocesses. In the example of FIG. 29, the first 16 HARQ processes andcorresponding IDs, support ACK/NACK in response to transmitted data,while the last 4 16 HARQ processes and corresponding IDs, are dedicatedHARQ suppression processes which do not support ACK/NACK in response totransmitted data.

FIG. 30 is a drawing 3000 illustrating an example of the first andsecond communications devices (2902, 2904) of FIG. 29, in which 4 of the20 HARQ processes are dedicated HARQ suppression processes, and furtherillustrating assignment of a first type of packet flow to a dedicatedHARQ suppression process, and assignment of a second type of packet flowto a HARQ process which does not suppress feedback of ACK/NACK for data.Drawing 3000 of FIG. 30 further includes legend 3001. Legend 3001identifies that the * symbol 2907 is used to indicate a HARQS process IDand corresponding HARQ process which is dedicate a HARQ suppressionprocess, e.g. in which ACK/NACK feedback for data is not communicated,expected, or used.

Legend 3001 further indicates that symbol 3009, which is a box including(PF1), is used to indicated which HARQ process packet flow 1, e.g., aTCP packet flow supporting end to end retransmission of packets, hasbeen assigned to. Legend 3001 further indicates that symbol 3011, whichis a box including (PF2), is used to indicate which HARQ process packetflow 2, e.g., a packet flow not supporting end to end retransmission ofpackets, has been assigned to.

Drawings 3000 illustrates, by use of the * symbol 2907, that HARQprocesses which are dedicated HARQ suppression processes are HARQprocess #17 with HARQS process ID=0, HARQ process #18 with HARQS processID=1, HARQ process #19 with HARQS process ID=2, and HARQ process #20with HARQS process ID=3.

Drawing 3000 further illustrates that packet flow 1, e.g., a TCP packetflow supporting end to end retransmission of packets, has been assignedto HARQ process #17 with HARQS process ID=0, which is a dedicated HARQsuppression process, which does not provide ACK/NACK feedback inresponse to transmitted data.

Drawing 3000 further illustrates that packet flow 2, e.g., a packet flowthat does not support end to end retransmission of packets, has beenassigned to HARQ process #1 with HARQ process ID=0, which is a normalHARQ process which supports ACK/NACK feedback in response to transmitteddata.

FIG. 31 is a drawing 3100 illustrating exemplary wireless communicationsdevices (wireless communications device 1 3102, wireless communicationsdevice 3104), exemplary signaling and exemplary steps of an exemplarymethod in which RLC ACK/NACK is conditionally suppressed based on thevalue of a No RLC Acknowledgment Required (NRAR) indicator bit includedan Acknowledged Mode Data (AMD) PDU in accordance with an exemplaryembodiment. In one exemplary embodiment, in which the transmitted AMPDUs are communicated in the downlink, wireless communications device 13102 is a base station, e.g., a gNB or an eNB, and wirelesscommunications device 2 3104 is a user equipment (UE) device. In anotherexemplary embodiment, in which the transmitted AM PDUs are communicatedin the uplink, wireless communications device 1 3104 is a base station,e.g., a gNB or an eNB, and wireless communications device 1 3102 is auser equipment (UE) device. The UE device is, e.g., UE 600 of FIG. 6,and the base station is, e.g., base station 700 of FIG. 7.

In step 3106, wireless communications device 1 3102 generates andtransmits AMD PDUs (3110, 3112, 3114, 3116, 3118, 3120) each AMD PDUincluding a NRAR field communicating a NRAR value. FIG. 5 illustratesexemplary format for exemplary AMD PDUs which include an NRAR field.Wireless signals 3108 transmitted from wireless communications device 13102 to wireless communications device 2 3104 communicates the AMD PDUs(AMD PDU 3110 including a sequence number (SN)=1 and a NRAR indicatorequal to 0, which indicates RLC acknowledgment expected, AMD PDU 3112including a sequence number (SN)=2 and a NRAR indicator equal to 0,which indicates RLC acknowledgment expected, AMD PDU 3114 including asequence number (SN=3 and a NRAR indicator equal to 1, which indicatesRLC acknowledgment not required, AMD PDU 3116 including a sequencenumber (SN)=4 and a NRAR indicator equal to 1, which indicates RLCacknowledgment not required, AMD PDU 3118 including a sequence number(SN)=5 and a NRAR indicator equal to 0, which indicates RLCacknowledgment expected, AMD PDU 3120 including a sequence number (SN)=6and a NRAR indicator equal to 0, which indicates

RLC acknowledgment expected.

In step 3122 the second wireless communications device receives the AMDPDUs (3110, 3112, 3114, 3116, 3118, 3120) including the NRAR field, andrecovers the communicated NRAR field indicator values. In step 3124, thesecond wireless communications device determines ACK/NACK to report forAMD PDUs in which the NRAR field value=0. In step 3126, the secondwireless communications device generates and transmits a RLC status PDU3130, which is communicated in transmitted wireless signal 3128. The RLCstatus PDU 3130 communicates ACK/NACK information corresponding to eachof the AMD PDUs with SN's 1, 2, 5 and 6, but does not communicateACK/NACK information corresponding to each of the AMD PDUs with SNs 3and 4.

In step 3132 wireless communications device 1 3102 receives the RLCstatus PDU, recovers the communicated information and retransmits inresponse to received NACKS corresspodning to previously transmitted PDUswith NRAR=0.

First Numbered Set of Exemplary Embodiments

Method Embodiment 1 A communications method, the method comprising:identifying (1204 or 2104), at a first wireless communications deviceincluding a transmitter, a first traffic flow; and transmitting (1208 or2110), from the first wireless communications device, an explicitindication to a second wireless communications device to skip HybridAutomatic Repeat Request (HARQ) feedback for data, corresponding to thefirst traffic flow, said data being transmitted to the second wirelesscommunications device.

Method Embodiment 2 The method of Method Embodiment 1, whereinidentifying (1204 or 2106) a first traffic flow includes: identifying(1206) a first traffic flow that supports an end to end retransmissionmethod in the event of a communications failure of data beingcommunicated.

Method Embodiment 3 The method of Method Embodiment 2, furthercomprising: identifying (1220 or 2120), at the first wirelesscommunications device a second traffic flow, said second traffic flowbeing a traffic flow which does not support an end to end retransmissionmethod; and transmitting (1222 or 2122) data to the second wirelesscommunications device without disabling HARQ feedback for the secondtraffic flow.

Method Embodiment 4 The method of Method Embodiment 2, wherein the firstwireless communications device is a first base station and the secondwireless communications device is a device which includes a wirelessreceiver for receiving data from said first base station; wherein saidfirst traffic flow is a downlink traffic flow; and wherein transmitting(1208) from the first wireless communications device, an explicitindication to a second wireless communications device to skip HARQfeedback for data includes: transmitting (1210) a Semi-PersistentScheduling (SPS) HARQ Off Indicator, set to indicate that HARQ isdisabled, in a radio configuration information element.

Method Embodiment 5 The method of Method Embodiment 4, wherein said SPSHARQ off indicator is a one bit value set to a predetermined value(e.g., 1) when HARQ is disabled.

Method Embodiment 6 The method of Method Embodiment 5, furthercomprising: transmitting (1214), from the first wireless communicationsdevice to the second wireless communications device, a HARQ OffIndicator, set to indicate that HARQ is disabled, said HARQ Offindicator being transmitted in field of a Downlink Control Information(DCI) Format scheduling message.

Method Embodiment 7 The method of Method Embodiment 6, wherein said HARQoff indicator is a one bit value set to a predetermined value (e.g., 1)when HARQ is disabled.

Method Embodiment 8 The method of claim 6, wherein said DCI Format isone of a DCI format 1_0 or DCI format 1_1.

Method Embodiment 9 The method of Method Embodiment 5, furthercomprising: operating (1216) the second wireless communications deviceto ignore at least one of i) information in a Physical Downlink SharedChannel (PDSCH)-to-HARQ feedback timing indicator field or ii)information in a HARQ process number field of downlink controlinformation provided by the first wireless communications device withrespect to the first traffic flow.

Method Embodiment 10 The method of Method Embodiment 2, wherein thefirst wireless communications device is a device (e.g., UE) whichincludes a transmitter for transmitting to a base station and the secondcommunications device is a base station which includes a wirelessreceiver for receiving data from said first wireless communicationsdevice (e.g., UE); and wherein said first traffic flow is an uplinktraffic flow.

Method Embodiment 11 The method of Method Embodiment 10, whereintransmitting (1208) from the first wireless communications device, anexplicit indication to a second wireless communications device to skipHARQ feedback for data includes: transmitting (1212) a Automatic Uplink(AUL) HARQ Off indicator to the base station.

Method Embodiment 12 The method of Method Embodiment 11, wherein the AULHARQ Off indicator is a one bit value set to a value indicating thatHARQ is disabled with respect to the first traffic flow.

Method Embodiment 13 The method of Method Embodiment 12, whereintransmitting (1218) the AUL HARQ Off indicator includes transmitting theindicator as part of an Autonomous Uplink-Uplink Control Information(AUL-UCI) that accompanies a Autonomous Uplink Physical Uplink SharedChannel (AUL-PUSCH) corresponding to the first traffic flow.

Method Embodiment 14 The method of Method Embodiment 2, wherein saidfirst traffic flow is a downlink traffic flow; wherein said firsttraffic flow data is uniquely intended for the second wirelesscommunications device; wherein said first traffic flow data is to besent using normal mode of communication; and wherein said transmitting(2110) an explicit indication to a second wireless communications deviceto skip Hybrid Automatic Repeat Request (HARQ) feedback for dataincludes: transmitting (2112), from the first wireless communicationsdevice to the second wireless communications device, a HARQ_Offindicator set to indicate HARQ is disabled in a downlink controlinformation (DCI) format scheduling message.

Method Embodiment 15 The method of Method Embodiment 14, wherein saidDCI format is DCI Format 1_0 or DCI Format 1_1.

Method Embodiment 16 The method of Method Embodiment 14, wherein in saidnormal mode of communications data is encoded via C-RNTI.

Method Embodiment 17 The method of Method Embodiment 2, wherein saidfirst traffic flow is a downlink traffic flow; wherein said firsttraffic flow data is uniquely intended for the second wirelesscommunications device; wherein said first traffic flow data is to besent using a Semi-Persistent Scheduling (SPS) mode of communication; andwherein said transmitting (2110) an explicit indication to a secondwireless communications device to skip Hybrid Automatic Repeat Request(HARQ) feedback for data includes: transmitting (2114), from the firstwireless communications device to the second wireless communicationsdevice, at least one of: i) a SPS HARQ Off Indicator set to indicateHARQ is set to disabled or ii) a HARQ_Off indicator set to indicate HARQis disabled in a downlink control information (DCI) format schedulingmessage.

Method Embodiment 18 The method of Method Embodiment 17, wherein saidDCI format is DCI Format 1_0 or DCI Format 1_1.

Method Embodiment 19 The method of Method Embodiment 17, wherein in saidSPS mode of communications data is encoded via SP-RNTI.

Second Numbered Set of Exemplary Embodiments

System Embodiment 1 A communications system comprising: a first wirelesscommunications device comprising: a transmitter; and a processorconfigured to: identify (1204 or 2104), at a first wirelesscommunications device including a transmitter, a first traffic flow; andoperate the transmitter to transmit (1208 or 2110), from the firstwireless communications device, an explicit indication to a secondwireless communications device to skip Hybrid Automatic Repeat Request(HARQ) feedback for data, corresponding to the first traffic flow, saiddata being transmitted to the second wireless communications device.

System Embodiment 2 The communications system of System Embodiment 1,wherein said processor is configured to: identify (1206) a first trafficflow that supports an end to end retransmission method in the event of acommunications failure of data being communicated, as part of beingconfigured to identify (1204 or 2106) a first traffic flow.

System Embodiment 3 The communications system of System Embodiment 2,wherein said processor is further configured to: identify (1220 or2120), at the first wireless communications device a second trafficflow, said second traffic flow being a traffic flow which does notsupport an end to end retransmission method; and operate the transmitterto transmit (1222 or 2122) data to the second wireless communicationsdevice without disabling HARQ feedback for the second traffic flow.

System Embodiment 4 The communications system of System Embodiment 2,wherein the first wireless communications device is a first base stationand the second wireless communications device is a device which includesa wireless receiver for receiving data from said first base station;wherein said first traffic flow is a downlink traffic flow; and whereinsaid processor is configured to operate said transmitter to transmit(1210) a Semi-Persistent Scheduling (SPS) HARQ Off Indicator, set toindicate that HARQ is disabled, in a radio configuration informationelement, as part of configured operate said transmitter to transmitter(1208) from the first wireless communications device, an explicitindication to a second wireless communications device to skip HARQfeedback for data.

System Embodiment 5 The communications system of System Embodiment 4,wherein said SPS HARQ off indicator is a one bit value set to apredetermined value (e.g., 1) when HARQ is disabled.

System Embodiment 6 The communications system of System Embodiment 5,wherein said processor is further configured to: operate saidtransmitter to transmit (1214), from the first wireless communicationsdevice to the second wireless communications device, a HARQ OffIndicator, set to indicate that HARQ is disabled, said HARQ Offindicator being transmitted in field of a Downlink Control Information(DCI) Format scheduling message.

System Embodiment 7 The communications system of System Embodiment 6,wherein said HARQ off indicator is a one bit value set to apredetermined value (e.g., 1) when HARQ is disabled.

System Embodiment 8 The communications system of System Embodiment 6,wherein said DCI Format is one of a DCI format 1_0 or DCI format 1_1.

System Embodiment 9 The communications system of System Embodiment 5,further comprising: said second wireless communications devicecomprising: a receiver; and a second processor, said second processorbeing configured to: operate (1216) the second wireless communicationsdevice to ignore at least one of i) information in a Physical DownlinkShared Channel (PDSCH)-to-HARQ feedback timing indicator field or ii)information in a HARQ process number field of downlink controlinformation provided by the first wireless communications device withrespect to the first traffic flow.

System Embodiment 10 The communications system of System Embodiment 2,wherein the first wireless communications device is a device (e.g., UE)which includes said transmitter for transmitting to a base station;wherein the second communications device is a base station whichincludes a wireless receiver for receiving data from said first wirelesscommunications device (e.g., UE); and wherein said first traffic flow isan uplink traffic flow.

System Embodiment 11 The communications system of System Embodiment 10,wherein said processor is configured to: operate the transmitter totransmit (1212) a Automatic Uplink (AUL) HARQ Off indicator to the basestation, as part of being configured to operate the transmitter totransmit (1208) from the first wireless communications device, anexplicit indication to a second wireless communications device to skipHARQ feedback for data.

System Embodiment 12 The communications system of System Embodiment 11,wherein the AUL HARQ Off indicator is a one bit value set to a valueindicating that HARQ is disabled with respect to the first traffic flow.

System Embodiment 13 The communications system of System Embodiment 12,wherein said processor is configured to operate said transmitter totransmit Autonomous Uplink-Uplink Control Information (AUL-UCI) thataccompanies a Autonomous Uplink Physical Uplink Shared Channel(AUL-PUSCH) corresponding to the first traffic flow, said AUL HARQ Offindicator being part of the AUL-UCI.

System Embodiment 14 The communications system of System Embodiment 2,wherein said first traffic flow is a downlink traffic flow; wherein saidfirst traffic flow data is uniquely intended for the second wirelesscommunications device; wherein said first traffic flow data is to besent using normal mode of communication; and wherein said processor isconfigured to operate said transmitter to transmit (2112), from thefirst wireless communications device to the second wirelesscommunications device, a HARQ Off indicator set to indicate HARQ isdisabled in a downlink control information (DCI) format schedulingmessage, as part of being configured to operate said transmitter totransmit (2110) an explicit indication to a second wirelesscommunications device to skip Hybrid Automatic Repeat Request (HARQ)feedback for data.

System Embodiment 15 The communications system of System Embodiment 14,wherein said DCI format is DCI Format 1_0 or DCI Format 1_1.

System Embodiment 16 The communications system of System Embodiment 14,wherein in said normal mode of communications data is encoded viaC-RNTI.

System Embodiment 17 The communications system of System Embodiment 2,wherein said first traffic flow is a downlink traffic flow; wherein saidfirst traffic flow data is uniquely intended for the second wirelesscommunications device; wherein said first traffic flow data is to besent using a Semi-Persistent Scheduling (SPS) mode of communication; andwherein said processor is configured to operate said transmitter totransmit (2114), from the first wireless communications device to thesecond wireless communications device, at least one of: i) a SPS HARQOff Indicator set to indicate HARQ is set to disabled or ii) a HARQ_Offindicator set to indicate HARQ is disabled in a downlink controlinformation (DCI) format scheduling message, as part of being configuredto operate said transmitter to transmit (2110) an explicit indication toa second wireless communications device to skip Hybrid Automatic RepeatRequest (HARQ) feedback for data.

System Embodiment 18 The communications system of System Embodiment 17,wherein said DCI format is DCI Format 1_0 or DCI Format 1_1.

System Embodiment 19 The communications system of System Embodiment 17,wherein in said SPS mode of communications data is encoded via SP-RNTI.

Third Numbered Set of Exemplary Embodiments

Computer Readable Medium Embodiment 1 A non-transitory computer readablemedium including computer executable instructions which when executed bya processor of a first wireless communications device cause the firstwireless communications device to perform the steps of: identifying(1204 or 2104), at a first wireless communications device including atransmitter, a first traffic flow; and transmitting (1208 or 2110), fromthe first wireless communications device, an explicit indication to asecond wireless communications device to skip Hybrid Automatic RepeatRequest (HARQ) feedback for data, corresponding to the first trafficflow, said data being transmitted to the second wireless communicationsdevice.

Fourth Numbered Set of Exemplary Embodiments

Method Embodiment 1 A method of operating a first communications device(e.g., base station (gNB or eNB) or user equipment (UE) device)including a transmitter, the method comprising: identifying (1504) afirst packet flow for which end to end retransmission of packets issupported; and assigning (1518) said first packet flow to a HybridAutomatic Repeat Request (HARQ) process which does not requiregeneration of acknowledgements (ACKs) or negative acknowledgements(NAKs) from a device receiving data corresponding to said packet flow;and transmitting (1526) data corresponding to said first packet flow toa second communications device (e.g. the second communications device isa UE device which includes a receiver and is one end of the packet flowwhich has a third communications device, e.g. a second UE or server,e.g., application server (AS), as the other packet flow end point or thesecond communications device is a base station, e.g., a gNB or eNB whichincludes a receiver).

Method Embodiment 2 The method of Method Embodiment 1, wherein said HARQprocess is a HARQ process for a TCP packet flow which supports end toend retransmission of packets, said HARQ process not supportingretransmission of data in response to a NACK and not requiringtransmission of ACKs/NACKs from the receiving device to which data wastransmitted.

Method Embodiment 3 The method of Method Embodiment 2, wherein said HARQprocess is a dedicated HARQ process for a flow for which suppression ofACK/NACK is required, said dedicated HARQ process for the flow nottriggering generation of ACK/NACK at the physical layer.

Method Embodiment 4 The method of Method Embodiment 1, wherein assigning(1518) said first packet flow to a HARQ process includes assigning(1520) said first packet flow to a HARQ process identified by a HARQprocess ID which is designated as indicating a HARQ suppression.

Method Embodiment 5 The method of Method Embodiment 4, wherein said HARQprocess ID for the first packet flow is communicated in a RRC IE (RadioResource Control Information Element).

Method Embodiment 6 The method of Method Embodiment 5, wherein said RRCIE is an Information Element (IE) of a Physical Downlink Control Channel(PDCCH).

Method Embodiment 7 The method of Method Embodiment 5, furthercomprising: transmitting (1522) said HARQ process ID for the firstpacket flow to the second communications device.

Method Embodiment 8 The method of Method Embodiment 7, whereintransmitting (1522) said HARQ process ID for the first packet flow tothe second communications device includes: transmitting (1524) said HARQprocess ID for the first packet flow to the second communications devicein an information element (IE) of a physical downlink control channel(PDCCH) (,e.g., of a RRC message).

Method Embodiment 9 The method of Method Embodiment 5, wherein said HARQprocess ID is a 4 bit ID.

Method Embodiment 10 The method of Method Embodiment 5, wherein thefirst communications device is a base station and the secondcommunications device is a UE; and wherein the RRC IE indicates a HARQprocess to be used for a corresponding transmission block (TB)transmitted in a downlink channel.

Method Embodiment 11 The method of Method Embodiment 4, wherein firstcommunications device is a UE and the second communications device is abase station; and wherein said HARQ process to which the first packetflow is assigned is to be used for a corresponding uplink (UL)transmission block (TB) transmitted in a uplink channel.

Method Embodiment 12 The method of Method Embodiment 1, furthercomprising: designating (1509) K HARQ process IDs, corresponding to KHARQ processes, to be used to mean no ACK/NACK expected, said K HARQprocesses to be used for transport blocks (TBs) on which HARQ is to besuppressed.

Method Embodiment 13 The method of Method Embodiment 12, furthercomprising: generating (1510) a radio resource control (RRC) messageincluding a RRC information element (IE) identifying the K HARQprocesses designated a No ACK/NACK expected.

Method Embodiment 14 The method of Method Embodiment 13, wherein saidRRC information element (IE) identifying the K HARQ processes designateda No ACK/NACK expected, is a four bit information element.

Method Embodiment 15 The method of Method Embodiment 13, furthercomprising: transmitting (1516) said generated RRC message, includingsaid RCC IE identifying the K HARQ processes designated as No ACK/NACK,to said second communications device.

Method Embodiment 16 The method of Method Embodiment 15, wherein saidfirst communications device is a base station; wherein said secondcommunications device is a user equipment (UE) device; wherein saidfirst packet flow is a downlink packet flow; and wherein generating(1510) a RRC control message includes: generating (1512) a RRC controlmessage including an RRC IE ‘HARQ process ID for suppression indownlink’, which communicates a value indicating which HARQ process IDsare to be used for Transport Blocks (TBs) in the downlink directionwhich do not require HARQ feedback to sender.

Method Embodiment 17 The method of Method Embodiment 16, whereingenerating (1512) a RRC control message including an RRC IE ‘HARQprocess ID for suppression in downlink’ includes: including (1513) insaid RRC message an RRC IE ‘HARQ process ID for suppression’ including avalue indicating the K number of HARQ processes designated as No HARQACK/NACK expected.

Method Embodiment 18 The method of Method Embodiment 17, wherein saidRRC IE ‘HARQ process ID for suppression’ is a 4 bit IE.

Method Embodiment 19 The method of Method Embodiment 15, wherein saidfirst communications device is a user equipment (UE) device; whereinsaid second communications device is a base station; wherein said firstpacket flow is an uplink packet flow; and wherein generating (1510) aRRC control message includes: generating (1514) a RRC control messageincluding an RRC IE ‘HARQ process ID for suppression in uplink’, whichcommunicates a value indicating which HARQ process IDs are to be used inthe uplink direction for Transport Blocks (TBs) identified to notrequire HARQ feedback from receiver.

Method Embodiment 20 The method of Method Embodiment 19, whereingenerating (1514) a RRC control message including an RRC IE ‘HARQprocess ID for suppression in uplink’ includes: including (1515) in saidRRC message an RRC IE ‘HARQ process ID for suppression’ including avalue indicating the K number of HARQ processes designated as No HARQACK/NACK expected.

Method Embodiment 21 The method of Method Embodiment 20, wherein saidRRC IE ‘HARQ process ID for suppression’ is a 4 bit IE.

Fifth Numbered Set of Exemplary Embodiments

Apparatus Embodiment 1 A first communications device (e.g., base station(gNB or eNB) or user equipment (UE) device) comprising: a transmitter;and a processor configured to: identify (1504) a first packet flow forwhich end to end retransmission of packets is supported; and assign(1518) said first packet flow to a Hybrid Automatic Repeat Request(HARQ) process which does not require generation of acknowledgements(ACKs) or negative acknowledgements (NAKs) from a device receiving datacorresponding to said packet flow; and operate said transmitter totransmit (1526) data corresponding to said first packet flow to a secondcommunications device (e.g. the second communications device is a UEdevice which includes a receiver and is one end of the packet flow whichhas a third communications device, e.g. a second UE or server, e.g.,application server (AS), as the other packet flow end point or thesecond communications device is a base station, e.g., a gNB or eNB whichincludes a receiver).

Apparatus Embodiment 2 The first communications device of ApparatusEmbodiment 1, wherein said HARQ process is a HARQ process for a TCPpacket flow which supports end to end retransmission of packets, saidHARQ process not supporting retransmission of data in response to a NACKand not requiring transmission of ACKs/NACKs from the receiving deviceto which data was transmitted.

Apparatus Embodiment 3 The first communications device of ApparatusEmbodiment 2, wherein said HARQ process is a dedicated HARQ process fora flow for which suppression of ACK/NACK is required, said dedicatedHARQ process for the flow not triggering generation of ACK/NACK at thephysical layer.

Apparatus Embodiment 4 The first communications device of ApparatusEmbodiment 1, wherein said processor is configured to assign (1520) saidfirst packet flow to a HARQ process identified by a HARQ process IDwhich is designated as indicating a HARQ suppression, as part of beingconfigured to assign (1518) said first packet flow to a HARQ process.

Apparatus Embodiment 5 The first communications device of firstcommunications device 4, wherein said HARQ process ID for the firstpacket flow is communicated in a RRC IE (Radio Resource ControlInformation Element).

Apparatus Embodiment 6 The first communications device of ApparatusEmbodiment 5, wherein said RRC IE is an Information Element (IE) of aPhysical Downlink Control Channel (PDCCH).

Apparatus Embodiment 7 The first communications device of ApparatusEmbodiment 5, wherein said processor is further configured to: operatesaid transmitter to transmit (1522) said HARQ process ID for the firstpacket flow to the second communications device.

Apparatus Embodiment 8 The first communications device of ApparatusEmbodiment 7, wherein said processor is configured to: operate saidtransmitter to transmit (1524) said HARQ process ID for the first packetflow to the second communications device in an information element (IE)of a physical downlink control channel (PDCCH) (,e.g., of a RRCmessage), as part of being configured to operate said transmitter totransmit (1522) said HARQ process ID for the first packet flow to thesecond communications device.

Apparatus Embodiment 9 The first communications device of ApparatusEmbodiment 5, wherein said HARQ process ID is a 4 bit ID.

Apparatus Embodiment 10 The first communications device of ApparatusEmbodiment 5, wherein first communications device is a base station andthe second communications device is a UE; and wherein the RRC IEindicates a HARQ process to be used for a corresponding transmissionblock (TB) transmitted in a downlink channel.

Apparatus Embodiment 11 The first communications device of ApparatusEmbodiment 4, wherein first communications device is a UE and the secondcommunications device is a base station; and wherein said HARQ processto which the first packet flow is assigned is to be used for acorresponding uplink (UL) transmission block (TB) transmitted in auplink channel.

Apparatus Embodiment 12 The first communications device of ApparatusEmbodiment 1, wherein said processor is further configured to: designate(1509) K HARQ process IDs, corresponding to K HARQ processes, to be usedto mean no ACK/NACK expected, said K HARQ processes to be used fortransport blocks (TBs) on which HARQ is to be suppressed.

Apparatus Embodiment 13 The first communications device of ApparatusEmbodiment 12, wherein said processor is further configured to: generate(1510) a radio resource control (RRC) message including a RRCinformation element (IE) identifying the K HARQ processes designated aNo ACK/NACK expected.

Apparatus Embodiment 14 The first communications device of ApparatusEmbodiment 13, wherein said RRC information element (IE) identifying theK HARQ processes designated a No ACK/NACK expected, is a four bitinformation element.

Apparatus Embodiment 15 The first communications device of ApparatusEmbodiment 13, wherein said processor is further configured to: operatesaid transmitter to transmit (1516) said generated RRC message,including said RCC IE identifying the K HARQ processes designated as NoACK/NACK, to said second communications device.

Apparatus Embodiment 16 The first communications device of ApparatusEmbodiment 15, wherein said first communications device is a basestation; wherein said second communications device is a user equipment(UE) device; wherein said first packet flow is a downlink packet flow;and wherein said processor is configured to generate (1512) a RRCcontrol message including an RRC IE ‘HARQ process ID for suppression indownlink’, which communicates a value indicating which HARQ process IDsare to be used for Transport Blocks (TBs) in the downlink directionwhich do not require HARQ feedback to sender, as part of beingconfigured to generate (1510) a RRC control message.

Apparatus Embodiment 17 The first communications device of ApparatusEmbodiment 16, wherein said processor is configured to: include (1513)in said RRC message an RRC IE ‘HARQ process ID for suppression’including a value indicating the K number of HARQ processes designatedas No HARQ ACK/NACK expected, as part of being configured to generate(1512) a RRC control message including an RRC IE ‘HARQ process ID forsuppression in downlink’.

Apparatus Embodiment 18 The first communications device of ApparatusEmbodiment 17, wherein said RRC IE ‘HARQ process ID for suppression’ isa 4 bit IE.

Apparatus Embodiment 19 The first communications device of ApparatusEmbodiment 15, wherein said first communications device is a userequipment (UE) device; wherein said second communications device is abase station; wherein said first packet flow is an uplink packet flow;and wherein said processor is configured to: generate (1514) a RRCcontrol message including an RRC IE ‘HARQ process ID for suppression inuplink’, which communicates a value indicating which HARQ process IDsare to be used in the uplink direction for Transport Blocks (TBs)identified to not require HARQ feedback from receiver, as part of beingconfigured to generate (1510) a RRC control message.

Apparatus Embodiment 20 The first communications device of ApparatusEmbodiment 19, wherein said processor is configured to: include (1515)in said RRC message an RRC IE ‘HARQ process ID for suppression’including a value indicating the K number of HARQ processes designatedas No HARQ ACK/NACK expected, as part of being configured to generate(1514) a RRC control message including an RRC IE ‘HARQ process ID forsuppression in uplink’.

Apparatus Embodiment 21 The first communications device of ApparatusEmbodiment 20, wherein said RRC IE ‘HARQ process ID for suppression’ isa 4 bit IE.

Sixth Numbered Set of Exemplary Embodiments

Computer Readable Medium Embodiment 1 A non-transitory computer readablemedium including computer executable instructions which when executed bya processor of a first communications device cause the firstcommunications device to perform the steps of: identifying (1504) afirst packet flow for which end to end retransmission of packets issupported; and assigning (1518) said first packet flow to a HybridAutomatic Repeat Request (HARQ) process which does not requiregeneration of acknowledgements (ACKs) or negative acknowledgements(NAKs) from a device receiving data corresponding to said packet flow;and

transmitting (1526) data corresponding to said first packet flow to asecond communications device (e.g. the second communications device is aUE device which includes a receiver and is one end of the packet flowwhich has a third communications device, e.g. a second UE or server,e.g., application server (AS), as the other packet flow end point or thesecond communications device is a base station, e.g., a gNB or eNB whichincludes a receiver).

Seventh Numbered Set of Exemplary Embodiments

Method Embodiment 1 A communications method comprising: identifying(1802), at a first wireless communications device (e.g., a base stationsuch as a gNB or eNB) including a transmitter, a first traffic flow; andtransmitting (1808), from the first wireless communications device, anexplicit indication in a downlink message to a second wirelesscommunications device (e.g., a UE) to skip Hybrid Automatic RepeatRequest (HARQ) feedback for data, corresponding to the first trafficflow, said data being directed to the second wireless communicationsdevice.

Method Embodiment 2 The communications method of Method Embodiment 1,wherein said second wireless communications device is an endpoint ofsaid first traffic flow.

Method Embodiment 3 The communications method of Method Embodiment 1,wherein said explicit indication to skip Hybrid Automatic Repeat Request(HARQ) feedback for data is a predetermined value in a predeterminedfield of a downlink control information (DCI) scheduling message.

Method Embodiment 4 The communications method of Method Embodiment 3,wherein said DCI scheduling message is one of a DCI format 1_0 or DCIformat 1_1 scheduling message.

Method Embodiment 5 The method of Method Embodiment 3, wherein saidpredetermined field is a ‘PDSCH-to-HARQ_feedback timing indicator’field.

Method Embodiment 6 The communications method of Method Embodiment 3,wherein, the predetermined value is a value outside an expected range ofvalues for a PDSCH-to-HARQ feedback timing indicator.

Method Embodiment 7 The communications method of Method Embodiment 3,further comprising: receiving (1810), at said second wirelesscommunications device, a downlink control information schedulingmessage; decoding (1812), at said second wireless communications device,said predetermined field of the DCI scheduling message; and determining(1814), at said second wireless communications device, whether or notthe predetermined field of the DCI scheduling message communicates thepredetermined value, which is the explicit indication to skip HybridAutomatic Repeat Request (HARQ) feedback for data.

Method Embodiment 8 The method of Method Embodiment 7, furthercomprising: when the determination is that the predetermined field ofthe DCI scheduling message communicates the predetermined value,operating (1820) the second wireless communications device to refrainfrom including HARQ-ACK in uplink control information (UCI) for codeblock groups (CBGs) and Transport Blocks (TBs) scheduled in the DCIscheduling message.

Method Embodiment 9 The method of Method Embodiment 8, furthercomprising: when the determination is that the predetermined field ofthe DCI scheduling message communicates does not communicate thepredetermined value, operating (1822) the second wireless communicationsdevice to include HARQ-ACK (HARQ ACK or HARQ NACK) in uplink controlinformation (UCI) for code block groups (CBGs) and Transport Blocks(TBs) scheduled in the DCI scheduling message.

Method Embodiment 10 The method of Method Embodiment 3, wherein saidpredetermined value is a specific value which is indicated via a higherlayer parameter.

Method Embodiment 11 The method of Method Embodiment 3, wherein saidhigher layer parameter is a Slot-timing-value-K1 parameter.

Method Embodiment 12 The method of Method Embodiment 3, whereinidentifying (1802) a first traffic flow includes: identifying (1804) afirst traffic flow that supports an end to end retransmission method inthe event of a communications failure of data being communicated.

Method Embodiment 13 The method of Method Embodiment 12, furthercomprising: transmitting (1816), from the first wireless communicationsdevice, data to the second wireless communications device with disabledHARQ feedback for the first traffic flow.

Method Embodiment 14 The method of Method Embodiment 12, wherein saidfirst traffic flow is a downlink traffic flow.

Method Embodiment 15 The method of Method Embodiment 12, furthercomprising: identifying (1824), at the first wireless communicationsdevice a second traffic flow, said second traffic flow being a trafficflow which does not support an end to end retransmission method; andtransmitting (1826), from the first wireless communications device, datato the second wireless communications device without disabling HARQfeedback for the second traffic flow.

Eighth Number Set of Exemplary Embodiments

System Embodiment 1 A communications system comprising: a first wirelesscommunications device comprising: a transmitter; and a processorconfigured to: identify (1802), at a first wireless communicationsdevice (e.g., a base station such as a gNB or eNB) including atransmitter, a first traffic flow; and operate said transmitter totransmit (1808), from the first wireless communications device, anexplicit indication in a downlink message to a second wirelesscommunications device (e.g., a UE) to skip Hybrid Automatic RepeatRequest (HARQ) feedback for data, corresponding to the first trafficflow, said data being directed to the second wireless communicationsdevice.

System Embodiment 2 The communications system of System Embodiment 1,wherein said second wireless communications device is an endpoint ofsaid first traffic flow.

System Embodiment 3 The communications system of System Embodiment 1,wherein said explicit indication to skip Hybrid Automatic Repeat Request(HARQ) feedback for data is a predetermined value in a predeterminedfield of a downlink control information (DCI) scheduling message.

System Embodiment 4 The communications system of System Embodiment 3,wherein said DCI scheduling message is one of a DCI format 1_0 or DCIformat 1_1 scheduling message.

System Embodiment 5 The communications system of System Embodiment 3,wherein said predetermined field is a ‘PDSCH-to-HARQ feedback timingindicator’ field.

System Embodiment 6 The communications system of System Embodiment 3,wherein, the predetermined value is a value outside an expected range ofvalues for a PDSCH-to-HARQ feedback timing indicator.

System Embodiment 7 The communications system of System Embodiment 3,wherein said system further comprises: said second wirelesscommunications device, said second wireless communications devicecomprising: a receiver; and a second processor configured to: operatesaid receiver to receive (1810), at said second wireless communicationsdevice, a downlink control information scheduling message; decode(1812), at said second wireless communications device, saidpredetermined field of the DCI scheduling message; and determine (1814),at said second wireless communications device, whether or not thepredetermined field of the DCI scheduling message communicates thepredetermined value, which is the explicit indication to skip HybridAutomatic Repeat Request (HARQ) feedback for data.

System Embodiment 8 The communications system of System Embodiment 7,wherein said second processor is further configured to: operate (1820)the second wireless communications device to refrain from includingHARQ-ACK in uplink control information (UCI) for code block groups(CBGs) and Transport Blocks (TBs) scheduled in the DCI schedulingmessage, when the determination is that the predetermined field of theDCI scheduling message communicates the predetermined value

System Embodiment 9 The communications system of System Embodiment 8,wherein said second processor is further configured to: operate (1822)the second wireless communications device to include HARQ-ACK (HARQ ACKor HARQ NACK) in uplink control information (UCI) for code block groups(CBGs) and Transport Blocks (TBs) scheduled in the DCI schedulingmessage, when the determination is that the predetermined field of theDCI scheduling message communicates does not communicate thepredetermined value,

System Embodiment 10 The communications system of System Embodiment 3,wherein said predetermined value is a specific value which is indicatedvia a higher layer parameter.

System Embodiment 11 The communications system of System Embodiment 3,wherein said higher layer parameter is a Slot-timing-value-K1 parameter.

System Embodiment 12 The communications of System Embodiment 3, whereinsaid processor is configured to: identify (1804) a first traffic flowthat supports an end to end retransmission method in the event of acommunications failure of data being communicated, as part of beingconfigured to identify (1802) a first traffic flow.

System Embodiment 13 The communications system of System Embodiment 12,wherein said processor is further configured to: operate saidtransmitter to transmit (1816), from the first wireless communicationsdevice, data to the second wireless communications device with disabledHARQ feedback for the first traffic flow.

System Embodiment 14 The communications system of System Embodiment 12,wherein said first traffic flow is a downlink traffic flow.

System Embodiment 15 The communications system of System Embodiment 12,wherein said processor is configured to: identify (1824), at the firstwireless communications device a second traffic flow, said secondtraffic flow being a traffic flow which does not support an end to endretransmission method; and operate said transmitter to transmit (1826),from the first wireless communications device, data to the secondwireless communications device without disabling HARQ feedback for thesecond traffic flow.

Ninth Numbered Set of Exemplary Embodiments

Computer Readable Medium Embodiment 1 A non-transitory computer readablemedium including computer executable instructions which when executed bya processor of a first wireless communications device cause the firstwireless communications device to perform the steps of: identifying(1802), at a first wireless communications device (e.g., a base stationsuch as a gNB or eNB) including a transmitter, a first traffic flow; andtransmitting (1808), from the first wireless communications device, anexplicit indication in a downlink message to a second wirelesscommunications device (e.g., a UE) to skip Hybrid Automatic RepeatRequest (HARQ) feedback for data, corresponding to the first trafficflow, said data being directed to the second wireless communicationsdevice.

Tenth Numbered Set of Exemplary Embodiments

Method Embodiment 1 A method of operating a first wirelesscommunications device including a radio transmitter, the methodcomprising; identifying (2304) a Packet Data Convergence Protocol (PDCP)packet corresponding to an Radio Link Control Acknowledged Mode (RLCAM); and generating (2306) an Acknowledged Mode Protocol Data Unit (AMPDU) including a No RLC ACK Required (NRAR) indicator; and operating(2322) the radio transmitter in the first wireless communications deviceto transmit the AM PDU to a second wireless communications device.

Method Embodiment 2 The method of Method Embodiment 1, wherein said AMPDU is an acknowledged mode data protocol data unit (AMD PDU).

Method Embodiment 3 The method of Method Embodiment 1, whereingenerating (2306) an Acknowledged Mode Protocol Data Unit (AM PDU)including a No RLC ACK required indicator includes: inserting (2310) theNo RLC ACK required indicator after a Sequence Number (SN) in aacknowledgement mode PDU with no Segment Offset (SO).

Method Embodiment 4 The method of Method Embodiment 1, whereingenerating (2306) an Acknowledged Mode Protocol Data Unit (AM PDU)including a No RLC ACK required indicator includes: including (2311) aSegment Offset in the AM PDU; and inserting (2312) the No RLC ACKrequired indicator after the Segment Offset (SO).

Method Embodiment 5 The method of Method Embodiment 1, wherein the NRARindicator is a one bit indicator.

Method Embodiment 6 The method of Method Embodiment 5, wherein the NRARindicator is the first bit in an octet.

Method Embodiment 7 The method of Method Embodiment 1, wherein the NRARindicator is set to one to indicate an RLC ACK is not required.

Method Embodiment 8 The method of Method Embodiment 1, wherein the NRARindicator is set to zero to indicate an RLC ACK is expected.

Method Embodiment 9 The method of Method Embodiment 8, furthercomprising: operating (2326) the first wireless communications device toreceive an RLC STATUS PDU from the second wireless communicationsdevice, said RLC status PDU including an ACK report from the secondwireless device.

Method Embodiment 10 The method of Method Embodiment 9, wherein said RLCstatus PDU includes a serial number or sequence number corresponding tothe transmitted AM PDU and an indication of ACK or NACK for thetransmitted PDU.

Method Embodiment 11 The method of Method Embodiment 8, furthercomprising: transmitting (2324) a second AM PDU including a No RLC ACKRequired (NRAR) indicator set to one indicating an RLC ACK is notrequired.

Method Embodiment 12. The method of Method Embodiment 11, wherein saidsecond AM PDU is a second acknowledged mode data protocol data unit (AMDPDU).

Method Embodiment 13 The method of Method Embodiment 11, furthercomprising: receiving (2326) from the second wireless communicationsdevice a RLC STATUS PDU, wherein said RLC STATUS PDU includes a sequencenumber and a ACK/NACK indication corresponding to the transmitted AM PDUwhich included a NRAR indicator set to zero, and wherein said RLC STATUSPDU does not include a sequence number or an ACK/NACK indicationcorresponding to the transmitted second AM PDU which included the statusbit set to one, said second wireless communications device havingintentionally left out the sequence number corresponding to the secondAM PDU.

Method Embodiment 14. The method of Method Embodiment 13, wherein saidACK/NACK indication corresponding to the transmitted PDU indicates NACK;and wherein said second transmitted PDU was successfully recovered bysaid second wireless device.

Eleventh Numbered Set of Exemplary Embodiments

Apparatus Embodiment 1 A first wireless communications devicecomprising: a radio transmitter; and a processor configured to: identify(2304) a Packet Data Convergence Protocol (PDCP) packet corresponding toan Radio Link Control Acknowledged Mode (RLC AM); and generate (2306) anAcknowledged Mode Protocol Data Unit (AM PDU) including a No RLC ACKRequired (NRAR) indicator; and operate (2322) the radio transmitter inthe first wireless communications device to transmit the AM PDU to asecond wireless communications device.

Apparatus Embodiment 2. The first wireless communication device of claim1, wherein said AM PDU is an acknowledged mode data protocol data unit(AMD PDU).

Apparatus Embodiment 3 The first wireless communications device ofApparatus Embodiment 1, wherein said processor is configured to: insert(2310) the No RLC ACK required indicator after a Sequence Number (SN) ina acknowledgement mode PDU with no Segment Offset (SO), as part of beingconfigured to generate (2306) an Acknowledged Mode Protocol Data Unit(AM PDU) including a No RLC ACK required indicator.

Apparatus Embodiment 4 The first wireless communications device ofApparatus Embodiment 1, wherein said processor is configured to: include(2311) a Segment Offset in the AM PDU; and insert (2312) the No RLC ACKrequired indicator after the Segment Offset (SO), as part of beingconfigured to generate (2306) an Acknowledged Mode Protocol Data Unit(AM PDU) including a No RLC ACK required indicator.

Apparatus Embodiment 5. The first wireless communications device ofApparatus Embodiment 1, wherein the NRAR indicator is a one bitindicator.

Apparatus Embodiment 6 The first wireless communications device ofApparatus Embodiment 5, wherein the NRAR indicator is the first bit inan octet.

Apparatus Embodiment 7 The first wireless communications device ofApparatus Embodiment 1, wherein the NRAR indicator is set to one toindicate an RLC ACK is not required.

Apparatus Embodiment 8 The first wireless communications device ofApparatus Embodiment 1, wherein the NRAR indicator is set to zero toindicate an RLC ACK is expected.

Apparatus Embodiment 9 The first wireless communications device ofApparatus Embodiment 8, further comprising: a receiver; and wherein saidprocessor is configured to operate (2326) receiver in the first wirelesscommunications device to receive an RLC STATUS PDU from the secondwireless communications device, said RLC status PDU including an ACKreport from the second wireless device.

Apparatus Embodiment 10 The first wireless communications device ofApparatus Embodiment 9, wherein said RLC status PDU includes a sequencenumber corresponding to the transmitted AM PDU and an indication of ACKor NACK for the transmitted PDU.

Apparatus Embodiment 11 The first wireless communications device ofApparatus Embodiment 8, wherein said processor is configured to: operatesaid transmitter to transmit (2324) a second AM PDU including a No RLCACK Required (NRAR) indicator set to one indicating an RLC ACK is notrequired.

Apparatus Embodiment 12 The first wireless communications device ofApparatus Embodiment 11, wherein said second AM PDU is a secondacknowledged mode data protocol data unit (AMD PDU).

Apparatus Embodiment 13 The first wireless communications device ofApparatus Embodiment 11, further comprising: a receiver; and whereinsaid processor is configured to operate said receiver to receive (2326)from the second wireless communications device a RLC STATUS PDU, whereinsaid RLC STATUS PDU includes a sequence number and a ACK/NACK indicationcorresponding to the transmitted AM PDU which included a NRAR indicatorset to zero, and wherein said RLC STATUS PDU does not include a sequencenumber or an ACK/NACK indication corresponding to the transmitted secondAM PDU which included the status bit set to one, said second wirelesscommunications device having intentionally left out the sequence numbercorresponding the second AM PDU.

Apparatus Embodiment 14 The first wireless communications device ofApparatus Embodiment 13, wherein said ACK/NACK indication correspondingto the transmitted AM PDU indicates NACK; and wherein said secondtransmitted AM PDU was successfully recovered by said second wirelessdevice.

Twelfth Number Set of Exemplary Embodiments

Computer Readable Medium Embodiment 1 A non-transitory computer readablemedium including computer executable instructions which when executed bya processor of a first wireless communications device including a radiotransmitter cause the first wireless communications device to performthe steps of: identifying (2304) a Packet Data Convergence Protocol(PDCP) packet corresponding to an Radio Link Control Acknowledged Mode(RLC AM); and generating (2306) an Acknowledged Mode Protocol Data Unit(AM PDU) including a No RLC ACK Required (NRAR) indicator; and operating(2322) the radio transmitter in the first wireless communications deviceto transmit the AM PDU to a second wireless communications device.

The techniques of various embodiments may be implemented using software,hardware and/or a combination of software and hardware. Variousembodiments are directed to apparatus, e.g., user devices, basestations, servers, customer premises equipment devices, cable systems,network nodes, gateways, cable headend/hubsites, network monitoringnode/servers, cluster controllers, cloud nodes, production nodes, cloudservices servers and/or network equipment devices. Various embodimentsare also directed to methods, e.g., method of controlling and/oroperating user devices, base stations, gateways, servers, cablenetworks, cloud networks, nodes, servers, cloud service servers,customer premises equipment devices, controllers, network monitoringnodes/servers and/or cable or network equipment devices. Variousembodiments are also directed to machine, e.g., computer, readablemedium, e.g., ROM, RAM, CDs, hard discs, etc., which include machinereadable instructions for controlling a machine to implement one or moresteps of a method. The computer readable medium is, e.g., non-transitorycomputer readable medium.

It is understood that the specific order or hierarchy of steps in theprocesses and methods disclosed is an example of exemplary approaches.Based upon design preferences, it is understood that the specific orderor hierarchy of steps in the processes and methods may be rearrangedwhile remaining within the scope of the present disclosure. Theaccompanying method claims present elements of the various steps in asample order, and are not meant to be limited to the specific order orhierarchy presented. In some embodiments, one or more processors areused to carry out one or more steps of the each of the describedmethods.

In various embodiments each of the steps or elements of a method areimplemented using one or more processors. In some embodiments, each ofelements are steps are implemented using hardware circuitry.

In various embodiments nodes and/or elements described herein areimplemented using one or more components to perform the stepscorresponding to one or more methods, for example, message reception,signal processing, sending, comparing, determining and/or transmissionsteps. Thus, in some embodiments various features are implemented usingcomponents or in some embodiments logic such as for example logiccircuits. Such components may be implemented using software, hardware ora combination of software and hardware. Many of the above describedmethods or method steps can be implemented using machine executableinstructions, such as software, included in a machine readable mediumsuch as a memory device, e.g., RAM, floppy disk, etc. to control amachine, e.g., general purpose computer with or without additionalhardware, to implement all or portions of the above described methods,e.g., in one or more nodes. Accordingly, among other things, variousembodiments are directed to a machine-readable medium, e.g., anon-transitory computer readable medium, including machine executableinstructions for causing a machine, e.g., processor and associatedhardware, to perform one or more of the steps of the above-describedmethod(s). Some embodiments are directed to a device, e.g., acontroller, including a processor configured to implement one, multipleor all of the steps of one or more methods of the invention.

In some embodiments, the processor or processors, e.g., CPUs, of one ormore devices, e.g., communications nodes such as controllers areconfigured to perform the steps of the methods described as beingperformed by the communications nodes, e.g., controllers. Theconfiguration of the processor may be achieved by using one or morecomponents, e.g., software components, to control processorconfiguration and/or by including hardware in the processor, e.g.,hardware components, to perform the recited steps and/or controlprocessor configuration. Accordingly, some but not all embodiments aredirected to a device, e.g., communications node such as a clustercontroller including, with a processor which includes a componentcorresponding to each of the steps of the various described methodsperformed by the device in which the processor is included. In some butnot all embodiments a device, e.g., communications node such as acontroller, includes a controller corresponding to each of the steps ofthe various described methods performed by the device in which theprocessor is included. The components may be implemented using softwareand/or hardware.

Some embodiments are directed to a computer program product comprising acomputer-readable medium, e.g., a non-transitory computer-readablemedium, comprising code for causing a computer, or multiple computers,to implement various functions, steps, acts and/or operations, e.g. oneor more steps described above. Depending on the embodiment, the computerprogram product can, and sometimes does, include different code for eachstep to be performed. Thus, the computer program product may, andsometimes does, include code for each individual step of a method, e.g.,a method of controlling a controller or node. The code may be in theform of machine, e.g., computer, executable instructions stored on acomputer-readable medium, e.g., a non-transitory computer-readablemedium, such as a RAM (Random Access Memory), ROM (Read Only Memory) orother type of storage device. In addition to being directed to acomputer program product, some embodiments are directed to a processorconfigured to implement one or more of the various functions, steps,acts and/or operations of one or more methods described above.Accordingly, some embodiments are directed to a processor, e.g., CPU,configured to implement some or all of the steps of the methodsdescribed herein. The processor may be for use in, e.g., acommunications device such as a controller or other device described inthe present application. In some embodiments components are implementedas hardware devices in such embodiments the components are hardwarecomponents. In other embodiments components may be implemented assoftware, e.g., a set of processor or computer executable instructions.Depending on the embodiment the components maybe all hardwarecomponents, all software components, a combination of hardware and/orsoftware or in some embodiments some components are hardware componentswhile other components are software components.

Numerous additional variations on the methods and apparatus of thevarious embodiments described above will be apparent to those skilled inthe art in view of the above description. Such variations are to beconsidered within the scope. Numerous additional embodiments, within thescope of the present invention, will be apparent to those of ordinaryskill in the art in view of the above description and the claims whichfollow. Such variations are to be considered within the scope of theinvention.

What is claimed is:
 1. A communications method comprising: identifying,at a first wireless communications device including a transmitter, afirst traffic flow; and transmitting, from the first wirelesscommunications device, an explicit indication in a downlink message to asecond wireless communications device to skip Hybrid Automatic RepeatRequest (HARQ) feedback for data, corresponding to the first trafficflow, said data being directed to the second wireless communicationsdevice.
 2. The communications method of claim 1, wherein said explicitindication to skip Hybrid Automatic Repeat Request (HARQ) feedback fordata is a predetermined value in a predetermined field of a downlinkcontrol information (DCI) scheduling message.
 3. The communicationsmethod of claim 2, wherein said DCI scheduling message is one of a DCIformat 1_0 or DCI format 1_1 scheduling message.
 4. The method of claim2, wherein said predetermined field is a ‘PDSCH-to-HARQ_feedback timingindicator’ field.
 5. The communications method of claim 2, wherein, thepredetermined value is a value outside an expected range of values for aPDSCH-to-HARQ feedback timing indicator.
 6. The communications method ofclaim 2, further comprising: receiving, at said second wirelesscommunications device, a downlink control information schedulingmessage; decoding, at said second wireless communications device, saidpredetermined field of the DCI scheduling message; and determining, atsaid second wireless communications device, whether or not thepredetermined field of the DCI scheduling message communicates thepredetermined value, which is the explicit indication to skip HybridAutomatic Repeat Request (HARQ) feedback for data.
 7. The method ofclaim 6, further comprising: when the determination is that thepredetermined field of the DCI scheduling message communicates thepredetermined value, operating the second wireless communications deviceto refrain from including HARQ-ACK in uplink control information (UCI)for code block groups (CBGs) and Transport Blocks (TBs) scheduled in theDCI scheduling message.
 8. The method of claim 7, further comprising:when the determination is that the predetermined field of the DCIscheduling message communicates does not communicate the predeterminedvalue, operating the second wireless communications device to includeHARQ-ACK (HARQ ACK or HARQ NACK) in uplink control information (UCI) forcode block groups (CBGs) and Transport Blocks (TBs) scheduled in the DCIscheduling message.
 9. The method of claim 2, wherein said predeterminedvalue is a specific value which is indicated via a higher layerparameter.
 10. The method of claim 2, wherein said higher layerparameter is a Slot-timing-value-K1 parameter.
 11. The method of claim2, wherein identifying (1802) a first traffic flow includes: identifyinga first traffic flow that supports an end to end retransmission methodin the event of a communications failure of data being communicated. 12.The method of claim 11, further comprising: transmitting (1816), fromthe first wireless communications device, data to the second wirelesscommunications device with disabled HARQ feedback for the first trafficflow.
 13. The method of claim 11, further comprising: identifying, atthe first wireless communications device a second traffic flow, saidsecond traffic flow being a traffic flow which does not support an endto end retransmission method; and transmitting, from the first wirelesscommunications device, data to the second wireless communications devicewithout disabling HARQ feedback for the second traffic flow.
 14. Acommunications system comprising: a first wireless communications devicecomprising: a transmitter; and a processor configured to: identify, at afirst wireless communications device including a transmitter, a firsttraffic flow; and operate said transmitter to transmit, from the firstwireless communications device, an explicit indication in a downlinkmessage to a second wireless communications device to skip HybridAutomatic Repeat Request (HARQ) feedback for data, corresponding to thefirst traffic flow, said data being directed to the second wirelesscommunications device.
 15. The communications system of claim 14,wherein said explicit indication to skip Hybrid Automatic Repeat Request(HARQ) feedback for data is a predetermined value in a predeterminedfield of a downlink control information (DCI) scheduling message. 16.The communications system of claim 15, wherein said DCI schedulingmessage is one of a DCI format 1_0 or DCI format 1_1 scheduling message.17. The communications system of claim 15, wherein said predeterminedfield is a ‘PDSCH-to-HARQ_feedback timing indicator’ field.
 18. Thecommunications system of claim 15, wherein said system furthercomprises: said second wireless communications device, said secondwireless communications device comprising: a receiver; and a secondprocessor configured to: operate said receiver to receive, at saidsecond wireless communications device, a downlink control informationscheduling message; decode, at said second wireless communicationsdevice, said predetermined field of the DCI scheduling message; anddetermine, at said second wireless communications device, whether or notthe predetermined field of the DCI scheduling message communicates thepredetermined value, which is the explicit indication to skip HybridAutomatic Repeat Request (HARQ) feedback for data.
 19. Thecommunications system of claim 18, wherein said second processor isfurther configured to: operate the second wireless communications deviceto refrain from including HARQ-ACK in uplink control information (UCI)for code block groups (CBGs) and Transport Blocks (TBs) scheduled in theDCI scheduling message, when the determination is that the predeterminedfield of the DCI scheduling message communicates the predetermined value20. A non-transitory computer readable medium including computerexecutable instructions which when executed by a processor of a firstwireless communications device cause the first wireless communicationsdevice to perform the steps of: identifying, at a first wirelesscommunications device including a transmitter, a first traffic flow; andtransmitting, from the first wireless communications device, an explicitindication in a downlink message to a second wireless communicationsdevice to skip Hybrid Automatic Repeat Request (HARQ) feedback for data,corresponding to the first traffic flow, said data being directed to thesecond wireless communications device.